From: Kees Cook <kees@kernel.org>
To: Alexander Mikhalitsyn <alexander@mihalicyn.com>
Cc: "Aleksa Sarai" <cyphar@cyphar.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andy Lutomirski" <luto@amacapital.net>,
"Will Drewry" <wad@chromium.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <shuah@kernel.org>,
"Tycho Andersen" <tycho@tycho.pizza>,
"Andrei Vagin" <avagin@gmail.com>,
"Christian Brauner" <brauner@kernel.org>,
"Stéphane Graber" <stgraber@stgraber.org>
Subject: Re: [PATCH v3 4/7] seccomp: mark first listener in the tree
Date: Wed, 28 Jan 2026 14:32:48 -0800 [thread overview]
Message-ID: <202601281432.8E0D84660C@keescook> (raw)
In-Reply-To: <a54303d478e4492977f8760b0f2d22894bfe604a.camel@mihalicyn.com>
On Wed, Jan 28, 2026 at 08:05:25PM +0100, Alexander Mikhalitsyn wrote:
> Yeah, I'm thinking about preparing a separate patches to address
> a quirky seccomp behavior we discussed during LPC and then resend this
> series.
Yeah, I'd love to see it as a distinct change. :)
--
Kees Cook
next prev parent reply other threads:[~2026-01-28 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 12:46 [PATCH v3 0/7] seccomp: support nested listeners Alexander Mikhalitsyn
2025-12-11 12:46 ` [PATCH v3 1/7] seccomp: remove unused argument from seccomp_do_user_notification Alexander Mikhalitsyn
2025-12-11 12:46 ` [PATCH v3 4/7] seccomp: mark first listener in the tree Alexander Mikhalitsyn
2026-01-21 12:22 ` Aleksa Sarai
2026-01-28 19:05 ` Alexander Mikhalitsyn
2026-01-28 22:32 ` Kees Cook [this message]
2025-12-11 12:46 ` [PATCH v3 6/7] seccomp: allow nested listeners Alexander Mikhalitsyn
2025-12-12 13:57 ` Andy Lutomirski
2026-01-28 19:10 ` Alexander Mikhalitsyn
2026-01-21 7:51 ` Andrei Vagin
2026-01-21 15:43 ` Aleksa Sarai
2026-01-21 17:59 ` Andy Lutomirski
2026-01-23 6:26 ` Andrei Vagin
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=202601281432.8E0D84660C@keescook \
--to=kees@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=avagin@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=cyphar@cyphar.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=stgraber@stgraber.org \
--cc=tycho@tycho.pizza \
--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