From: Kees Cook <keescook@chromium.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Kees Cook" <keescook@chromium.org>,
"Christian Brauner" <brauner@kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Robert Święcki" <robert@swiecki.net>,
"Jann Horn" <jannh@google.com>, "Oleg Nesterov" <oleg@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: [PATCH 0/2] exit: Introduce __WCHILDSIGINFO for waitid
Date: Mon, 14 Feb 2022 13:38:21 -0800 [thread overview]
Message-ID: <20220214213823.3297816-1-keescook@chromium.org> (raw)
Hi,
Okay, here's a working version of this. Is adding 48 bytes into task
struct worth it? Can this be improved, and is the non-signal-exit logic
for __WCHILDSIGINFO sane?
Other thoughts?
-Kees
Kees Cook (2):
exit: Introduce __WCHILDSIGINFO for waitid
selftests/seccomp: Check for waitid() behavior
include/linux/sched.h | 1 +
include/uapi/linux/wait.h | 1 +
kernel/exit.c | 23 +++-
kernel/signal.c | 4 +
tools/testing/selftests/seccomp/seccomp_bpf.c | 130 ++++++++++++++++++
5 files changed, 155 insertions(+), 4 deletions(-)
--
2.30.2
next reply other threads:[~2022-02-14 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 21:38 Kees Cook [this message]
2022-02-14 21:38 ` [PATCH 1/2] exit: Introduce __WCHILDSIGINFO for waitid Kees Cook
2022-02-15 9:14 ` Christian Brauner
2022-02-14 21:38 ` [PATCH 2/2] selftests/seccomp: Check for waitid() behavior Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220214213823.3297816-1-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=robert@swiecki.net \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).