Skip to content

ptrace: Stop supporting SIGKILL for PTRACE_EVENT_EXIT

Eric W. Biederman linux-alpha linux-ia64 linux-pm linux-um lkml stable 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 7 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3signal: Ensure SIGNAL_GROUP_EXIT gets set in do_group_exitkernel/exit.c+1 -10 replies
2/3signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exitinclude/linux/sched/signal.h kernel/exit.c kernel/fork.c+21 -00 replies
3/3signal: Drop signals received after a fatal signal has been processedfs/coredump.c kernel/signal.c+3 -20 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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