From: "Serge E. Hallyn" <serge@hallyn.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
Casey Schaufler <casey@schaufler-ca.com>,
LSM <linux-security-module@vger.kernel.org>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: security_task_prctl: why -ENOSYS
Date: Mon, 1 Jun 2026 14:33:46 -0500 [thread overview]
Message-ID: <ah3emjW3jOzQEX0/@mail.hallyn.com> (raw)
In-Reply-To: <CAFftDdqyTrr=wS2hUT1EvAqVsbegPRh9Y-rH5S3VEpvXbJ6QRg@mail.gmail.com>
On Mon, Jun 01, 2026 at 02:01:07PM -0500, William Roberts wrote:
> <snip>
> >
> > How about security_task_prctl_allowed()? (Mirroring security_uring_*)
> >
> > Renaming the existing hook security_task_prctl_handle() also wouldn't
> > be too bad, but that's probably more churn than it's worth.
> >
>
> Yeah if something else is already done, I'll just copy their
> convention. I went with suffix _check for now.
>
> Another possible issue that I think other upstream communities may
> have with adding an additional hook, is that there will be two hooks
> in the prctl syscall path,
> I am not sure if that's a show stopper?
It's not a hot path, so I wouldn't think so.
prev parent reply other threads:[~2026-06-01 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 22:39 security_task_prctl: why -ENOSYS William Roberts
2026-05-26 23:21 ` William Roberts
2026-05-26 23:42 ` Casey Schaufler
2026-05-27 16:05 ` William Roberts
2026-05-29 22:58 ` Serge E. Hallyn
2026-06-01 19:01 ` William Roberts
2026-06-01 19:33 ` Serge E. Hallyn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ah3emjW3jOzQEX0/@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=bill.c.roberts@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox