From: Oleg Nesterov <oleg@redhat.com>
To: Max Ver <dudududumaxver@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Kees Cook <kees@kernel.org>, Dmitry Levin <ldv@strace.io>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Will Drewry <wad@chromium.org>
Subject: Re: Process killed by seccomp looks live by tracer
Date: Sun, 22 Mar 2026 14:40:30 +0100 [thread overview]
Message-ID: <ab_xTq5MHu1yq3Sd@redhat.com> (raw)
In-Reply-To: <aa103dEXEqU4QlgZ@redhat.com>
On 03/08, Oleg Nesterov wrote:
> Perhaps you are right, but this is a question for seccomp experts...
>
> Kees, Andy, what do you think?
no comments ;)
Kees, Andy, I think that Max has a point. I'll send the RFC patch in
a minute.
Please review.
Oleg.
prev parent reply other threads:[~2026-03-22 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 10:51 Process killed by seccomp looks live by tracer Max Ver
2026-03-04 18:05 ` Kees Cook
2026-03-05 2:00 ` Max Ver
2026-03-05 14:49 ` Oleg Nesterov
2026-03-05 17:45 ` Oleg Nesterov
2026-03-06 2:55 ` Max Ver
2026-03-08 13:08 ` Oleg Nesterov
2026-03-22 13:40 ` Oleg Nesterov [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=ab_xTq5MHu1yq3Sd@redhat.com \
--to=oleg@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=dudududumaxver@gmail.com \
--cc=kees@kernel.org \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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