From: Kees Cook <kees@kernel.org>
To: Jamie Hill-Daniel <clubby789@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org, Jamie Hill-Daniel <jamie@hill-daniel.co.uk>
Subject: Re: [PATCH RESEND 0/2] seccomp: Allow using `SECCOMP_MODE_STRICT` with `SECCOMP_MODE_FILTER`
Date: Mon, 15 Jun 2026 15:38:33 -0700 [thread overview]
Message-ID: <202606151535.F32ACD538@keescook> (raw)
In-Reply-To: <CAO1UbGcbueeqLPOFA+=cJKjQxgXr1pW1vGFR-zNOT7rqsUqs+w@mail.gmail.com>
On Mon, Jun 15, 2026 at 05:23:53PM +0100, Jamie Hill-Daniel wrote:
> On Sat, Jun 13, 2026 at 5:14 AM Kees Cook <kees@kernel.org> wrote:
> > On Tue, May 26, 2026 at 04:32:14PM +0100, Jamie Hill-Daniel wrote:
> > > Link: https://github.com/moby/moby/issues/42082
> >
> > This doesn't show any particular application, just a demo program.
> >
> > I'd *really* prefer to only add complexity to seccomp if it is
> > absolutely needed.
>
> When I filed the original issue it was attempting a minimised
> reproduction; I was trying to run some legacy binary in a container
> that I unfortunately don't have the context for any more.
> I've submitted another series that should hopefully address some of
> the concerns raised here, including complexity.
Right, I think I'd prefer the legacy binary be adjusted instead. And not
adding complexity to seccomp given the issue isn't actually a problem
any more. :)
--
Kees Cook
next prev parent reply other threads:[~2026-06-15 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 15:32 [PATCH RESEND 0/2] seccomp: Allow using `SECCOMP_MODE_STRICT` with `SECCOMP_MODE_FILTER` Jamie Hill-Daniel
2026-05-26 15:32 ` [PATCH RESEND 1/2] " Jamie Hill-Daniel
2026-06-12 19:25 ` Will Drewry
2026-06-12 21:24 ` Andy Lutomirski
2026-06-12 22:01 ` clubby789
2026-06-12 22:37 ` Andy Lutomirski
2026-06-12 22:58 ` clubby789
2026-06-12 22:37 ` clubby789
2026-06-12 22:50 ` Andy Lutomirski
2026-05-26 15:32 ` [PATCH RESEND 2/2] selftest: seccomp: Adjust test for using both `STRICT` and `FILTER` Jamie Hill-Daniel
2026-06-13 4:14 ` [PATCH RESEND 0/2] seccomp: Allow using `SECCOMP_MODE_STRICT` with `SECCOMP_MODE_FILTER` Kees Cook
2026-06-15 16:23 ` Jamie Hill-Daniel
2026-06-15 22:38 ` Kees Cook [this message]
2026-06-15 23:16 ` Kees Cook
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=202606151535.F32ACD538@keescook \
--to=kees@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clubby789@gmail.com \
--cc=jamie@hill-daniel.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--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