diff options
| author | Christian Brauner <[email protected]> | 2025-04-11 15:09:44 +0000 |
|---|---|---|
| committer | Christian Brauner <[email protected]> | 2025-04-12 12:04:53 +0000 |
| commit | a9d7de0f68b79e5e481967fc605698915a37ac13 (patch) | |
| tree | c038848db5e8c37bcc784fb5602c370c7c560099 /net/unix/af_unix.c | |
| parent | Merge patch series "pidfd: improve uapi when task isn't found" (diff) | |
| parent | pidfs: ensure consistent ENOENT/ESRCH reporting (diff) | |
| download | kernel-a9d7de0f68b79e5e481967fc605698915a37ac13.tar.gz kernel-a9d7de0f68b79e5e481967fc605698915a37ac13.zip | |
Merge patch series "pidfs: ensure consistent ENOENT/ESRCH reporting"
Christian Brauner <[email protected]> says:
In a prior patch series we tried to cleanly differentiate between:
(1) The task has already been reaped.
(2) The caller requested a pidfd for a thread-group leader but the pid
actually references a struct pid that isn't used as a thread-group
leader.
as this was causing issues for non-threaded workloads.
But there's cases where the current simple logic is wrong. Specifically,
if the pid was a leader pid and the check races with __unhash_process().
Stabilize this by using the pidfd waitqueue lock.
* patches from https://lore.kernel.org/[email protected]:
pidfs: ensure consistent ENOENT/ESRCH reporting
exit: move wake_up_all() pidfd waiters into __unhash_process()
Link: https://lore.kernel.org/[email protected]
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions
