[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250409084446.GA2771@lst.de>
Date: Wed, 9 Apr 2025 10:44:46 +0200
From: Christoph Hellwig <hch@....de>
To: Kuniyuki Iwashima <kuniyu@...zon.com>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Peijie Shao <shaopeijie@...tc.cn>,
Kuniyuki Iwashima <kuni1840@...il.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme-tcp: Fix use-after-free of netns by kernel TCP
socket.
Thanks, applied to nvme-6.15.
> To fix such problems, let's hold netns ref by sk_net_refcnt_upgrade().
>
> We had the same issue in CIFS, SMC, etc, and applied the same
> solution, see commit ef7134c7fc48 ("smb: client: Fix use-after-free
> of network namespace.") and commit 9744d2bf1976 ("smc: Fix
> use-after-free in tcp_write_timer_handler().").
I wish the netns APIs would be a little more robus to prevent these
bugs from creeping in everywhere..
Powered by blists - more mailing lists