From: Oleg Nesterov <oleg@redhat.com>
To: Kusaram Devineni <kusaram@devineni.in>
Cc: Kees Cook <kees@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>, Will Drewry <wad@chromium.org>,
Max Ver <dudududumaxver@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ptrace: don't report syscall-exit if the tracee was killed by seccomp
Date: Sun, 5 Apr 2026 17:57:35 +0200 [thread overview]
Message-ID: <adKGb5vkyggMK-_l@redhat.com> (raw)
In-Reply-To: <adEhVv1-_oTG9NBa@redhat.com>
On 04/04, Oleg Nesterov wrote:
>
> On 04/03, Kusaram Devineni wrote:
> >
> OK, this is another (although related) issue, lets discuss it separately.
Yes...
> > For that specific path, one approach that seems to work is making signalfd
> > exclude
> > SA_IMMUTABLE signals from the mask it passes to
>
> Perhaps... But this is nasty.
OK, lets do it. I'll send the patch in a minute. It was already tested by syzbot.
Sorry, forgot to CC you, see https://lore.kernel.org/all/adJvw9gEC9D1Gxtq@redhat.com/
I don't see a better fix for now. Hopefully we can cleanup this later.
I think force_exit_sig / force_sig_seccomp should make fatal_signal_pending()
true, but we need a simple fix...
Oleg.
next prev parent reply other threads:[~2026-04-05 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 13:44 [RFC PATCH] ptrace: don't report syscall-exit if the tracee was killed by seccomp Oleg Nesterov
2026-03-22 14:47 ` Kees Cook
2026-03-22 15:14 ` Oleg Nesterov
2026-03-23 12:09 ` Oleg Nesterov
2026-04-03 15:26 ` Kusaram Devineni
2026-04-03 15:48 ` Oleg Nesterov
2026-04-03 17:16 ` Kusaram Devineni
2026-04-04 14:33 ` Oleg Nesterov
2026-04-05 15:57 ` Oleg Nesterov [this message]
2026-04-06 10:43 ` Kusaram Devineni
2026-03-22 16:36 ` Andrew Morton
2026-03-22 17:32 ` Oleg Nesterov
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=adKGb5vkyggMK-_l@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dudududumaxver@gmail.com \
--cc=kees@kernel.org \
--cc=kusaram@devineni.in \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.