[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250408055549.16568-1-kuniyu@amazon.com>
Date: Mon, 7 Apr 2025 22:55:27 -0700
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <hch@....de>
CC: <axboe@...nel.dk>, <gechangzhong@...tc.cn>, <kbusch@...nel.org>,
<kuniyu@...zon.com>, <linux-kernel@...r.kernel.org>,
<linux-nvme@...ts.infradead.org>, <netdev@...r.kernel.org>,
<sagi@...mberg.me>, <shaopeijie@...tc.cn>, <zhang.guanghui@...tc.cn>
Subject: Re: [PATCH v2] nvme-tcp: Fix netns UAF introduced by commit 1be52169c348
From: Christoph Hellwig <hch@....de>
Date: Tue, 8 Apr 2025 07:04:08 +0200
> On Mon, Apr 07, 2025 at 10:18:18AM -0700, Kuniyuki Iwashima wrote:
> > The followup patch is wrong, and the correct fix is to take a reference
> > to the netns by sk_net_refcnt_upgrade().
>
> Can you send a formal patch for this?
For sure.
Which branch/tag should be based on, for-next or nvme-6.15 ?
http://git.infradead.org/nvme.git
Powered by blists - more mailing lists