From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>,
kernel test robot <oliver.sang@intel.com>,
Mark Brown <broonie@kernel.org>,
Terry Tritton <terry.tritton@linaro.org>,
Tycho Andersen <tandersen@netflix.com>,
Will Drewry <wad@chromium.org>
Subject: [GIT PULL] seccomp updates for v6.9-rc1
Date: Mon, 11 Mar 2024 16:41:24 -0700 [thread overview]
Message-ID: <202403111640.68D9B74844@keescook> (raw)
Hi Linus,
Please pull these several seccomp updates for v6.9-rc1. There are no core
kernel changes here; it's entirely selftests and samples. Details below.
Thanks!
-Kees
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.9-rc1
for you to fetch changes up to 56af94aace8a0489fb1a32fd6f1cf0c548fe3911:
samples: user-trap: fix strict-aliasing warning (2024-02-12 10:42:02 -0800)
----------------------------------------------------------------
seccomp updates for v6.9-rc1
- Improve reliability of selftests (Terry Tritton, Kees Cook)
- Fix strict-aliasing warning in samples (Arnd Bergmann)
----------------------------------------------------------------
Arnd Bergmann (1):
samples: user-trap: fix strict-aliasing warning
Kees Cook (1):
selftests/seccomp: Pin benchmark to single CPU
Terry Tritton (3):
selftests/seccomp: Handle EINVAL on unshare(CLONE_NEWPID)
selftests/seccomp: Change the syscall used in KILL_THREAD test
selftests/seccomp: user_notification_addfd check nextfd is available
samples/seccomp/user-trap.c | 8 +++--
.../testing/selftests/seccomp/seccomp_benchmark.c | 38 ++++++++++++++++++--
tools/testing/selftests/seccomp/seccomp_bpf.c | 41 ++++++++++++++++------
3 files changed, 73 insertions(+), 14 deletions(-)
--
Kees Cook
next reply other threads:[~2024-03-11 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 23:41 Kees Cook [this message]
2024-03-12 22:24 ` [GIT PULL] seccomp updates for v6.9-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=202403111640.68D9B74844@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oliver.sang@intel.com \
--cc=tandersen@netflix.com \
--cc=terry.tritton@linaro.org \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).