summaryrefslogtreecommitdiff
path: root/fs/coredump.c
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2022-01-08 20:01:12 +0300
committerEric W. Biederman <ebiederm@xmission.com>2022-01-08 21:43:12 +0300
commit7ba03471ac4ad2432e5ccf67d9d4ab03c177578a (patch)
tree08726dd4a9c9a1790f46e3c71be88ea9e1b2fdcc /fs/coredump.c
parenta0287db0f1d6918919203ba31fd7cda59bf889e8 (diff)
downloadlinux-7ba03471ac4ad2432e5ccf67d9d4ab03c177578a.tar.xz
signal: Make coredump handling explicit in complete_signal
Ever since commit 6cd8f0acae34 ("coredump: ensure that SIGKILL always kills the dumping thread") it has been possible for a SIGKILL received during a coredump to set SIGNAL_GROUP_EXIT and trigger a process shutdown (for a second time). Update the logic to explicitly allow coredumps so that coredumps can set SIGNAL_GROUP_EXIT and shutdown like an ordinary process. Link: https://lkml.kernel.org/r/87zgo6ytyf.fsf_-_@email.froward.int.ebiederm.org Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'fs/coredump.c')
0 files changed, 0 insertions, 0 deletions