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>
Subject: [GIT PULL] seccomp fixes for v5.13-rc4
Date: Sat, 29 May 2021 11:16:59 -0700 [thread overview]
Message-ID: <202105291116.B0B7D78D8@keescook> (raw)
Hi Linus,
Please pull these seccomp fixes for v5.13-rc4. This fixes a hard-to-hit
race condition in the addfd user_notif feature of seccomp, visible since
v5.9.
Thanks!
-Kees
The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc:
Linux 5.13-rc2 (2021-05-16 15:27:44 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-fixes-v5.13-rc4
for you to fetch changes up to ddc473916955f7710d1eb17c1273d91c8622a9fe:
seccomp: Refactor notification handler to prepare for new semantics (2021-05-29 11:13:27 -0700)
----------------------------------------------------------------
seccomp fixes for v5.13-rc4
- Fix addfd notification race condition (Sargun Dhillon)
----------------------------------------------------------------
Sargun Dhillon (2):
Documentation: seccomp: Fix user notification documentation
seccomp: Refactor notification handler to prepare for new semantics
Documentation/userspace-api/seccomp_filter.rst | 16 +++++++-------
kernel/seccomp.c | 30 ++++++++++++++------------
2 files changed, 24 insertions(+), 22 deletions(-)
--
Kees Cook
next reply other threads:[~2021-05-29 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 18:16 Kees Cook [this message]
2021-05-30 4:30 ` [GIT PULL] seccomp fixes for v5.13-rc4 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=202105291116.B0B7D78D8@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 \
/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