mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Bradley Morgan <brads@mainlining.org>,
	Cong Wang <cwang@multikernel.io>, Hui Peng <benquike@gmail.com>,
	Kees Cook <kees@kernel.org>
Subject: [GIT PULL] seccomp updates for v7.4-rc1
Date: Thu, 22 Oct 2026 10:53:07 -0700	[thread overview]
Message-ID: <202610221051.2E6D9ADDB1@keescook> (raw)

Hi Linus,

Please pull these seccomp updates for v7.4-rc1. These are mainly
improvements to USER_NOTIF behaviors.

Thanks!

-Kees

The following changes since commit df2908090cda368b01ff43709f51890076c56157:

  Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v7.4-rc1

for you to fetch changes up to e32008340585a12783045c4426fbb963cfa11b7e:

  selftests/seccomp: Split fork_and_close into clone and close tests (2026-10-06 02:02:49 -0700)

----------------------------------------------------------------
seccomp updates for v7.4-rc1

- allow addfd to transfer O_PATH descriptors (Cong Wang)

- allow restarting interrupted unreceived notifications (Cong Wang)

- fix SECCOMP_ADDFD_FLAG_SEND when interrupted (Hui Peng)

- Various docs and test clean-ups

----------------------------------------------------------------
Cong Wang (5):
      seccomp: allow restarting interrupted unreceived notifications
      selftests/seccomp: cover restart of unreceived notifications
      docs/seccomp: describe the SECCOMP_FILTER_FLAG_RESTART_BEFORE_RECV flag
      seccomp: allow addfd to transfer O_PATH descriptors
      selftests/seccomp: test addfd with an O_PATH descriptor

Hui Peng (1):
      seccomp: restore knotif->state when SECCOMP_ADDFD_FLAG_SEND is interrupted

Kees Cook (2):
      seccomp: Document RESTART_BEFORE_RECV and O_PATH addfd
      selftests/seccomp: Split fork_and_close into clone and close tests

 Documentation/userspace-api/seccomp_filter.rst |  37 ++
 include/linux/seccomp.h                        |   3 +-
 include/uapi/linux/seccomp.h                   |   2 +
 tools/include/uapi/linux/seccomp.h             |   2 +
 kernel/seccomp.c                               |  26 +-
 tools/testing/selftests/seccomp/seccomp_bpf.c  | 642 +++++++++++++++++++++++++
 6 files changed, 704 insertions(+), 8 deletions(-)

-- 
Kees Cook

                 reply	other threads:[~2026-10-22 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202610221051.2E6D9ADDB1@keescook \
    --to=kees@kernel.org \
    --cc=benquike@gmail.com \
    --cc=brads@mainlining.org \
    --cc=cwang@multikernel.io \
    --cc=linux-kernel@vger.kernel.org \
    --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 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®