From: Oleg Nesterov <oleg@redhat.com>
To: Bradley Morgan <include@grrlz.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ebiederm@xmission.com, Christian Brauner <brauner@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Adrian Huang <adrianhuang0701@gmail.com>,
Marco Elver <elver@google.com>,
Kexin Sun <kexinsun@smail.nju.edu.cn>,
Thomas Gleixner <tglx@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] signal: avoid shared siginfo namespace rewrites
Date: Fri, 26 Jun 2026 17:06:19 +0200 [thread overview]
Message-ID: <aj6Va2nNBZvDJqP5@redhat.com> (raw)
In-Reply-To: <FC7EAB84-0845-4DA3-AD43-3B30B47507E5@grrlz.net>
On 06/26, Bradley Morgan wrote:
>
> On June 26, 2026 3:29:07 PM GMT+01:00, Oleg Nesterov <oleg@redhat.com>
> wrote:
> >To avoid the confusion, let me reply to V1 again.
> >
> >Acked-by: Oleg Nesterov <oleg@redhat.com>
> >
> >IIUC Eric is fine with this change too.
> >
> >Andrew, can you take this fix please? We will send more changes on top
> >of it.
>
> Thanks again oleg.
>
> Andrew did reply to V2.
OOPS... where? I didn't get any email from him in this thread...
Oleg.
next prev parent reply other threads:[~2026-06-26 15:06 UTC|newest]
Thread overview: 16+ 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-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 [this message]
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=aj6Va2nNBZvDJqP5@redhat.com \
--to=oleg@redhat.com \
--cc=adrianhuang0701@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=include@grrlz.net \
--cc=kexinsun@smail.nju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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.