From: Andrew Morton <akpm@linux-foundation.org>
To: Bradley Morgan <include@grrlz.net>
Cc: Oleg Nesterov <oleg@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
Marco Elver <elver@google.com>,
Aleksandr Nogikh <nogikh@google.com>,
Thomas Gleixner <tglx@kernel.org>,
Adrian Huang <adrianhuang0701@gmail.com>,
Kexin Sun <kexinsun@smail.nju.edu.cn>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] signal: avoid shared siginfo namespace rewrites
Date: Sun, 28 Jun 2026 12:11:19 -0700 [thread overview]
Message-ID: <20260628121119.b2803aca486dc697bd142d00@linux-foundation.org> (raw)
In-Reply-To: <86a8857d58d43ee26a8b365b837fd24830343494.1782159692.git.include@grrlz.net>
On Mon, 22 Jun 2026 20:25:08 +0000 Bradley Morgan <include@grrlz.net> wrote:
> send_signal_locked() rewrites sender ids for the target namespace.
> Group sends reuse the same siginfo, so one recipient can affect the
> next.
>
> Copy the siginfo before changing it.
Thanks, I'll queue this for 7.3-rc1. I don't see a need to fast-track
it into mainline, as 7a0cf094944e is from 2019.
Can someone please send along a paragraph which describes the
userspace-visible effects of the bug? I think this is important when
proposing a backportable fix. Important for all fixes, really.
I understand that I'm to take no action with "[PATCH v2 2/2] signal:
make send_signal_locked() take const siginfo".
next prev parent reply other threads:[~2026-06-28 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 16:40 [PATCH] signal: avoid shared siginfo namespace rewrites Bradley Morgan
2026-06-22 17:46 ` Oleg Nesterov
2026-06-22 20:05 ` Bradley Morgan
2026-06-22 20:25 ` [PATCH v2 1/2] " Bradley Morgan
2026-06-23 11:37 ` Oleg Nesterov
2026-06-24 15:29 ` Eric W. Biederman
2026-06-24 15:52 ` Oleg Nesterov
2026-06-24 15:54 ` Bradley Morgan
2026-06-24 16:32 ` Oleg Nesterov
2026-06-28 19:11 ` Andrew Morton [this message]
2026-06-22 20:25 ` [PATCH v2 2/2] signal: make send_signal_locked() take const siginfo Bradley Morgan
2026-06-23 10:39 ` Oleg Nesterov
2026-06-23 14:49 ` Bradley Morgan
2026-06-26 14:29 ` [PATCH] signal: avoid shared siginfo namespace rewrites Oleg Nesterov
2026-06-26 14:36 ` Bradley Morgan
2026-06-26 15:06 ` Oleg Nesterov
2026-06-26 15:08 ` Bradley Morgan
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=20260628121119.b2803aca486dc697bd142d00@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adrianhuang0701@gmail.com \
--cc=brauner@kernel.org \
--cc=elver@google.com \
--cc=include@grrlz.net \
--cc=kexinsun@smail.nju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=nogikh@google.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.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.