From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Andrei Vagin <avagin@google.com>,
Christian Brauner <brauner@kernel.org>,
Kees Cook <kees@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
Tycho Andersen <tandersen@netflix.com>
Subject: [GIT PULL] seccomp updates for v6.11-rc1
Date: Mon, 15 Jul 2024 09:23:54 -0700 [thread overview]
Message-ID: <202407150923.7A3B3FD@keescook> (raw)
Hi Linus,
Please pull this seccomp update for v6.11-rc1.
Thanks!
-Kees
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.11-rc1
for you to fetch changes up to f0c508faea645da58d6ae6b644a1b68020d5a9d2:
selftests/seccomp: check that a zombie leader doesn't affect others (2024-06-28 09:37:11 -0700)
----------------------------------------------------------------
seccomp updates for v6.11-rc1
- interrupt SECCOMP_IOCTL_NOTIF_RECV when all users exit (Andrei Vagin)
- Update selftests to check for expected NOTIF_RECV exits (Andrei Vagin)
----------------------------------------------------------------
Andrei Vagin (4):
seccomp: interrupt SECCOMP_IOCTL_NOTIF_RECV when all users have exited
seccomp: release task filters when the task exits
selftests/seccomp: add test for NOTIF_RECV and unused filters
selftests/seccomp: check that a zombie leader doesn't affect others
kernel/exit.c | 3 +-
kernel/seccomp.c | 30 ++++--
tools/testing/selftests/seccomp/seccomp_bpf.c | 131 ++++++++++++++++++++++++++
3 files changed, 157 insertions(+), 7 deletions(-)
--
Kees Cook
next reply other threads:[~2024-07-15 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 16:23 Kees Cook [this message]
2024-07-16 21:43 ` [GIT PULL] seccomp updates for v6.11-rc1 pr-tracker-bot
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=202407150923.7A3B3FD@keescook \
--to=kees@kernel.org \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tandersen@netflix.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.