ptrace: Stop supporting SIGKILL for PTRACE_EVENT_EXIT
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | signal: Ensure SIGNAL_GROUP_EXIT gets set in do_group_exitkernel/ | +1 | 0 replies | |
| 2/3 | signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exitinclude/ kernel/ kernel/ | +21 | 0 replies | |
| 3/3 | signal: Drop signals received after a fatal signal has been processedfs/ kernel/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] ptrace: Stop supporting SIGKILL for PTRACE_EVENT_EXIT
Recently I had a conversation where it was pointed out to me that SIGKILL sent to a tracee stropped in PTRACE_EVENT_EXIT is quite difficult for a tracer to handle.
Keeping SIGKILL working for anything after the process has been killed is also a real pain from an implementation point of view.
So I am attempting to remove this wart in the userspace API and see if anyone cares.
Eric W. Biederman (3):
signal: Ensure SIGNAL_GROUP_EXIT gets set in do_group_exit
signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exit
signal: Drop signals received after a fatal signal has been processed
fs/coredump.c | 2 +- include/linux/sched/signal.h | 1 + kernel/exit.c | 20 +++++++++++++++++++- kernel/fork.c | 2 ++ kernel/signal.c | 3 ++- 5 files changed, 25 insertions(+), 3 deletions(-)
Eric