From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
Kees Cook <keescook@chromium.org>,
Rodrigo Campos <rodrigo@kinvolk.io>,
Sargun Dhillon <sargun@sargun.me>,
Tycho Andersen <tycho@tycho.pizza>,
Will Drewry <wad@chromium.org>
Subject: [GIT PULL] seccomp updates for v5.14-rc1
Date: Mon, 28 Jun 2021 12:57:16 -0700 [thread overview]
Message-ID: <202106281254.440E6D926@keescook> (raw)
Hi Linus,
Please pull these seccomp updates for v5.14-rc1. Note that the commit
dates show "today", but this has been in -next for a while. I didn't
correctly manage my "for-linus/seccomp" fixes branch (which this is
based on) that was pulled for v5.13-rc4.
Thanks!
-Kees
The following changes since commit ddc473916955f7710d1eb17c1273d91c8622a9fe:
seccomp: Refactor notification handler to prepare for new semantics (2021-05-29 11:13:27 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.14-rc1
for you to fetch changes up to 9a03abc16c77062c73972df08206f1031862d9b4:
selftests/seccomp: Avoid using "sysctl" for report (2021-06-28 12:49:52 -0700)
----------------------------------------------------------------
seccomp updates for v5.14-rc1
Add "atomic addfd + send reply" mode to SECCOMP_USER_NOTIF to better
handle EINTR races visible to seccomp monitors. (Rodrigo Campos,
Sargun Dhillon)
Improve seccomp selftests for readability in CI systems. (Kees Cook)
----------------------------------------------------------------
Kees Cook (3):
selftests/seccomp: More closely track fds being assigned
selftests/seccomp: Flush benchmark output
selftests/seccomp: Avoid using "sysctl" for report
Rodrigo Campos (2):
seccomp: Support atomic "addfd + send reply"
selftests/seccomp: Add test for atomic addfd+send
Documentation/userspace-api/seccomp_filter.rst | 12 +++++
include/uapi/linux/seccomp.h | 1 +
kernel/seccomp.c | 51 +++++++++++++++++++---
.../testing/selftests/seccomp/seccomp_benchmark.c | 10 ++++-
tools/testing/selftests/seccomp/seccomp_bpf.c | 51 ++++++++++++++++++++--
5 files changed, 113 insertions(+), 12 deletions(-)
--
Kees Cook
next reply other threads:[~2021-06-28 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 19:57 Kees Cook [this message]
2021-06-29 3:50 ` 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=202106281254.440E6D926@keescook \
--to=keescook@chromium.org \
--cc=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo@kinvolk.io \
--cc=sargun@sargun.me \
--cc=torvalds@linux-foundation.org \
--cc=tycho@tycho.pizza \
--cc=wad@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®