From: Oleg Nesterov <oleg@redhat.com>
To: "Cen Zhang (Microsoft)" <blbllhy@gmail.com>
Cc: joel.granados@kernel.org, kees@kernel.org, brauner@kernel.org,
mingo@redhat.com, peterz@infradead.org,
akpm@linux-foundation.org, jack@suse.cz, avagin@gmail.com,
ptikhomirov@virtuozzo.com, mjguzik@gmail.com, include@grrlz.net,
ebiederm@xmission.com, legion@kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
AutonomousCodeSecurity@microsoft.com,
tgopinath@linux.microsoft.com, kys@microsoft.com,
stable@vger.kernel.org
Subject: Re: [PATCH v4] reboot: fix cad_pid use-after-free race
Date: Fri, 14 Aug 2026 20:03:15 +0200 [thread overview]
Message-ID: <an9YY8DzjiDLa2tr@redhat.com> (raw)
In-Reply-To: <20260814040944.16561-1-blbllhy@gmail.com>
On 08/14, Cen Zhang (Microsoft) wrote:
>
> v4:
> - Rebase on sysctl-next after Oleg's cad_pid sysctl placement change.
> - Fold the two-patch v3 series into a single lifetime fix.
> - Move kill_cad_pid() implementation to kernel/signal.c.
> - Export kill_cad_pid() and stop exporting the raw cad_pid pointer.
> - Update proc_do_cad_pid() in kernel/reboot.c.
> - Add explicit includes for the RCU API and kill_cad_pid().
> - Preserve the original unprivileged impact context while noting that
> the namespace permission path has been fixed separately.
I don't see other changes in this version, so
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
prev parent reply other threads:[~2026-08-14 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 4:09 [PATCH v4] reboot: fix cad_pid use-after-free race Cen Zhang (Microsoft)
2026-08-14 9:22 ` Bradley Morgan
2026-08-14 18:03 ` 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=an9YY8DzjiDLa2tr@redhat.com \
--to=oleg@redhat.com \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=blbllhy@gmail.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=include@grrlz.net \
--cc=jack@suse.cz \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=kys@microsoft.com \
--cc=legion@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjguzik@gmail.com \
--cc=peterz@infradead.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=stable@vger.kernel.org \
--cc=tgopinath@linux.microsoft.com \
/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