diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-11-11 01:02:08 +0100 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-11-11 01:02:08 +0100 |
commit | 6752de1aebee8e73ee9cc31263407fdf0e29c274 (patch) | |
tree | 07fc268a1caba899409838fd3f9ba5eb5fbfd8d2 /kernel/sched | |
parent | Merge tag 'thermal-5.16-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/g... (diff) | |
parent | mm: use pidfd_get_task() (diff) | |
download | linux-6752de1aebee8e73ee9cc31263407fdf0e29c274.tar.xz linux-6752de1aebee8e73ee9cc31263407fdf0e29c274.zip |
Merge tag 'pidfd.v5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux
Pull pidfd updates from Christian Brauner:
"Various places in the kernel have picked up pidfds.
The two most recent additions have probably been the ability to use
pidfds in bpf maps and the usage of pidfds in mm-based syscalls such
as process_mrelease() and process_madvise().
The same pattern to turn a pidfd into a struct task exists in two
places. One of those places used PIDTYPE_TGID while the other one used
PIDTYPE_PID even though it is clearly documented in all pidfd-helpers
that pidfds __currently__ only refer to thread-group leaders (subject
to change in the future if need be).
This isn't a bug per se but has the potential to be one if we allow
pidfds to refer to individual threads. If that happens we want to
audit all codepaths that make use of them to ensure they can deal with
pidfds refering to individual threads.
This adds a simple helper to turn a pidfd into a struct task making it
easy to grep for such places. Plus, it gets rid of code-duplication"
* tag 'pidfd.v5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux:
mm: use pidfd_get_task()
pid: add pidfd_get_task() helper
Diffstat (limited to 'kernel/sched')
0 files changed, 0 insertions, 0 deletions