public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>,
	Colin Ian King <colin.i.king@gmail.com>,
	David Yang <davidcomponentone@gmail.com>,
	Jann Horn <jannh@google.com>, Kees Cook <keescook@chromium.org>,
	linux-kselftest@vger.kernel.org,
	Sargun Dhillon <sargun@sargun.me>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Tycho Andersen <tycho@tycho.pizza>,
	Yang Guang <yang.guang5@zte.com.cn>
Subject: [GIT PULL] seccomp updates for v5.19-rc1
Date: Mon, 23 May 2022 12:15:01 -0700	[thread overview]
Message-ID: <202205231214.ED9D18F@keescook> (raw)

Hi Linus,

Please pull these seccomp updates for v5.19-rc1.

Thanks!

-Kees

The following changes since commit 2bfed7d2ffa5d86c462d3e2067f2832eaf8c04c7:

  selftests/seccomp: Don't call read() on TTY from background pgrp (2022-04-29 11:28:41 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.19-rc1

for you to fetch changes up to 5e91d2a4146946ea0abc984ca957f12b70632901:

  selftests/seccomp: Fix spelling mistake "Coud" -> "Could" (2022-05-04 13:31:21 -0700)

----------------------------------------------------------------
seccomp updates for v5.19-rc1

- Rework USER_NOTIF notification ordering and kill logic (Sargun Dhillon)

- Improved PTRACE_O_SUSPEND_SECCOMP selftest (Jann Horn)

- Gracefully handle failed unshare() in selftests (Yang Guang)

- Spelling fix (Colin Ian King)

----------------------------------------------------------------
Colin Ian King (1):
      selftests/seccomp: Fix spelling mistake "Coud" -> "Could"

Jann Horn (1):
      selftests/seccomp: Test PTRACE_O_SUSPEND_SECCOMP without CAP_SYS_ADMIN

Sargun Dhillon (5):
      seccomp: Use FIFO semantics to order notifications
      selftests/seccomp: Ensure that notifications come in FIFO order
      seccomp: Add wait_killable semantic to seccomp user notifier
      selftests/seccomp: Refactor get_proc_stat to split out file reading code
      selftests/seccomp: Add test for wait killable notifier

Yang Guang (1):
      selftests/seccomp: Add SKIP for failed unshare()

 Documentation/userspace-api/seccomp_filter.rst |  10 +
 include/linux/seccomp.h                        |   3 +-
 include/uapi/linux/seccomp.h                   |   2 +
 kernel/seccomp.c                               |  44 ++-
 tools/testing/selftests/seccomp/Makefile       |   1 +
 tools/testing/selftests/seccomp/seccomp_bpf.c  | 427 ++++++++++++++++++++++++-
 6 files changed, 482 insertions(+), 5 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2022-05-23 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 19:15 Kees Cook [this message]
2022-05-24 19:53 ` [GIT PULL] seccomp updates for v5.19-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=202205231214.ED9D18F@keescook \
    --to=keescook@chromium.org \
    --cc=brauner@kernel.org \
    --cc=colin.i.king@gmail.com \
    --cc=davidcomponentone@gmail.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sargun@sargun.me \
    --cc=skhan@linuxfoundation.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tycho@tycho.pizza \
    --cc=yang.guang5@zte.com.cn \
    /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