Re: [PATCH 3/4] seccomp: Add SECCOMP_USER_NOTIF_FLAG_PIDFD to get pidfd on listener trap

From
Tycho Andersen <hidden>
Date
2020-01-26 05:42:56
Also in
linux-fsdevel, lkml
Reply to
Sargun Dhillon, 2020-01-24
On Fri, Jan 24, 2020 at 12:09:37PM -0800, Sargun Dhillon wrote:
On Fri, Jan 24, 2020 at 10:03 AM Tycho Andersen [off-list ref] wrote:
quoted
On Fri, Jan 24, 2020 at 01:17:42AM -0800, Sargun Dhillon wrote:
quoted
Currently, this just opens the group leader of the thread that triggere
the event, as pidfds (currently) are limited to group leaders.
I don't love the semantics of this; when they're not limited to thread
group leaders any more, we won't be able to change this. Is that work
far off?

Tycho
We would be able to change this in the future if we introduced a flag like
SECCOMP_USER_NOTIF_FLAG_PIDFD_THREAD which would send a
pidfd that's for the thread, and not just the group leader. The flag could
either be XOR with SECCOMP_USER_NOTIF_FLAG_PIDFD, or
could require both. Alternatively, we can rename
SECCOMP_USER_NOTIF_FLAG_PIDFD to
SECCOMP_USER_NOTIF_FLAG_GROUP_LEADER_PIDFD.
Ok, but then isn't this just another temporary API? Seems like it's
worth waiting until the Right Way exists.

Tycho
Thread (12 messages) 12 messages, 4 authors, last reply 2020-01-27
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help