[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r13gd4xy.fsf_-_@email.froward.int.ebiederm.org>
Date: Wed, 22 Jun 2022 11:43:37 -0500
From: "Eric W. Biederman" <ebiederm@...ssion.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
bigeasy@...utronix.de, Peter Zijlstra <peterz@...radead.org>,
Jann Horn <jannh@...gle.com>,
Kees Cook <keescook@...omium.org>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Robert O'Callahan <roc@...nos.co>, Kyle Huey <khuey@...nos.co>,
Keno Fischer <keno@...iacomputing.com>
Subject: [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
Powered by blists - more mailing lists