From: Kees Cook <kees@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Sargun Dhillon <sargun@sargun.me>,
Shuah Khan <shuah@kernel.org>,
Johannes Nixdorf <johannes@nixdorf.dev>
Cc: Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, Ali Polatel <alip@chesswob.org>,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2 0/2] seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast
Date: Tue, 29 Jul 2025 13:34:21 -0700 [thread overview]
Message-ID: <175382125844.1703528.15225839014415526576.b4-ty@kernel.org> (raw)
In-Reply-To: <20250725-seccomp-races-v2-0-cf8b9d139596@nixdorf.dev>
On Fri, 25 Jul 2025 18:31:17 +0200, Johannes Nixdorf wrote:
> If WAIT_KILLABLE_RECV was specified, and an event is received, the
> tracee's syscall is not supposed to be interruptible. This was not properly
> ensured if the reply was sent too fast, and an interrupting signal was
> received before the reply was processed on the tracee side.
>
> This series fixes the bug and adds a test case for it to the selftests.
>
> [...]
With minor edits, applied to for-next/seccomp, thanks!
[1/2] seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast
https://git.kernel.org/kees/c/cce436aafc2a
[2/2] selftests/seccomp: Add a test for the WAIT_KILLABLE_RECV fast reply race
https://git.kernel.org/kees/c/b0c9bfbab925
Take care,
--
Kees Cook
prev parent reply other threads:[~2025-07-29 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 16:31 [PATCH v2 0/2] seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast Johannes Nixdorf
2025-07-25 16:31 ` [PATCH v2 1/2] " Johannes Nixdorf
2025-07-25 16:31 ` [PATCH v2 2/2] selftests/seccomp: Add a test for the WAIT_KILLABLE_RECV fast reply race Johannes Nixdorf
2025-07-29 1:07 ` Kees Cook
2025-07-29 16:45 ` Johannes Nixdorf
2025-07-29 20:34 ` Kees Cook [this message]
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=175382125844.1703528.15225839014415526576.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=alip@chesswob.org \
--cc=bpf@vger.kernel.org \
--cc=johannes@nixdorf.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=sargun@sargun.me \
--cc=shuah@kernel.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