summaryrefslogtreecommitdiffstats
path: root/lib/test_module.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-10-09 16:14:15 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2022-10-09 16:14:15 -0700
commite572410e47a4e9647d5d7a49ca699a1497378707 (patch)
tree63396033a8fbca957d492db0ac00610d12384f5d /lib/test_module.c
parent86fb9c53d82f1dadf960553a3bd351de6173911f (diff)
parent9a95f78eab70deeb5a4c879c19b841a6af5b66e7 (diff)
downloadlinux-e572410e47a4e9647d5d7a49ca699a1497378707.tar.bz2
Merge tag 'signal-for-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace
Pull ptrace update from Eric Biederman: "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 after the process has been killed is pain from an implementation point of view. So since the debuggers don't want this behavior let's see if we can remove this wart for the userspace API If a regression is detected it should only need to be the last change that is the reverted. The other two are just general cleanups that make the last patch simpler" * tag 'signal-for-v5.20' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace: signal: Drop signals received after a fatal signal has been processed signal: Guarantee that SIGNAL_GROUP_EXIT is set on process exit signal: Ensure SIGNAL_GROUP_EXIT gets set in do_group_exit
Diffstat (limited to 'lib/test_module.c')
0 files changed, 0 insertions, 0 deletions