public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Ali Polatel <alip@chesswob.org>,
	Johannes Nixdorf <johannes@nixdorf.dev>,
	Kees Cook <kees@kernel.org>
Subject: [GIT PULL] seccomp updates for v6.18-rc1
Date: Mon, 29 Sep 2025 12:07:59 -0700	[thread overview]
Message-ID: <202509291207.66FBEC8497@keescook> (raw)

Hi Linus,

Please pull this seccomp update for v6.18-rc1.

Thanks!

-Kees

The following changes since commit e04c78d86a9699d136910cfc0bdcf01087e3267e:

  Linux 6.16-rc2 (2025-06-15 13:49:41 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.18-rc1

for you to fetch changes up to b0c9bfbab925ac6385d4d06a134fd89cadf771fe:

  selftests/seccomp: Add a test for the WAIT_KILLABLE_RECV fast reply race (2025-07-29 13:33:02 -0700)

----------------------------------------------------------------
seccomp updates for v6.18-rc1

- Fix race with WAIT_KILLABLE_RECV (Johannes Nixdorf)

----------------------------------------------------------------
Johannes Nixdorf (2):
      seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast
      selftests/seccomp: Add a test for the WAIT_KILLABLE_RECV fast reply race

 kernel/seccomp.c                              |  12 +--
 tools/testing/selftests/seccomp/seccomp_bpf.c | 131 ++++++++++++++++++++++++++
 2 files changed, 136 insertions(+), 7 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2025-09-29 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 19:07 Kees Cook [this message]
2025-09-30  1:13 ` [GIT PULL] seccomp updates for v6.18-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=202509291207.66FBEC8497@keescook \
    --to=kees@kernel.org \
    --cc=alip@chesswob.org \
    --cc=johannes@nixdorf.dev \
    --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