diff options
| author | Christian Brauner <brauner@kernel.org> | 2026-10-05 10:09:39 -0500 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-10-12 10:58:21 +0200 |
| commit | 3209535cd39e492074d5519ecf5721605bea3a26 (patch) | |
| tree | a8ca7fd616d13e436569ae1cb84fc15a0d5453cf /tools/lib/python | |
| parent | 02e658dffe501640079ad78c8fdd7eb6e1a5e4dc (diff) | |
| download | linux-next-3209535cd39e492074d5519ecf5721605bea3a26.tar.gz linux-next-3209535cd39e492074d5519ecf5721605bea3a26.zip | |
pidfs: record the coredump on the dumping thread's pid too
If a thread-group coredumps only the thread-group leader pidfd will
return coredump information. A pidfd for the thread that took the fatal
signal cannot be used to retrieve it.
Record both the thread-group leader and the specific thread that took
the signal and register both in pidfs. Mark both the thread-group leader
and the specific thread with the coredump information so retrieval works
for both pidfds.
Now that both SO_PEERPIDFD and SO_PEERPIDFD_THREAD are available it's
easy to get the coredump information for the specific thread.
Reviewed-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@futurfusion.io>
Signed-off-by: Andrew Halaney <andrew@amutable.com>
Link: https://patch.msgid.link/20261005-work-unix-passpidfd-v4-9-350183b6e02a@amutable.com
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
