[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250802080403.GW222315@ZenIV>
Date: Sat, 2 Aug 2025 09:04:03 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: 高翔 <gaoxiang17@...omi.com>
Cc: Xiang Gao <gxxa03070307@...il.com>,
"brauner@...nel.org" <brauner@...nel.org>,
"oleg@...hat.com" <oleg@...hat.com>,
"mjguzik@...il.com" <mjguzik@...il.com>,
"Liam.Howlett@...cle.com" <Liam.Howlett@...cle.com>,
"joel.granados@...nel.org" <joel.granados@...nel.org>,
"lorenzo.stoakes@...cle.com" <lorenzo.stoakes@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 答复: 答复: [External Mail]Re: [PATCH] pid: Add a judgment for ns null in pid_nr_ns
On Sat, Aug 02, 2025 at 06:38:20AM +0000, 高翔 wrote:
> I see, but does adding the judgment for ns make the code more robust?
It's an impossible condition for anything that runs in a context where
get_current() is allowed, so... I don't see any benefit in adding it.
Powered by blists - more mailing lists