[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250602050817.GA21900@lst.de>
Date: Mon, 2 Jun 2025 07:08:17 +0200
From: Christoph Hellwig <hch@....de>
To: Kuniyuki Iwashima <kuni1840@...il.com>
Cc: hch@....de, axboe@...nel.dk, chuck.lever@...cle.com,
davem@...emloft.net, edumazet@...gle.com, horms@...nel.org,
jaka@...ux.ibm.com, jlayton@...nel.org, kbusch@...nel.org,
kuba@...nel.org, kuniyu@...zon.com, linux-nfs@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-rdma@...r.kernel.org,
matttbe@...nel.org, mptcp@...ts.linux.dev, netdev@...r.kernel.org,
pabeni@...hat.com, sfrench@...ba.org, wenjia@...ux.ibm.com,
willemb@...gle.com
Subject: Re: [PATCH v2 net-next 3/7] socket: Restore sock_create_kern().
On Thu, May 29, 2025 at 07:53:41PM -0700, Kuniyuki Iwashima wrote:
> In the old days, sock_create_kern() did take a ref to netns,
> but an implicit change that avoids taking the ref has caused
> a lot of problems for people who used to the old semantics.
>
> This series rather rolls back the change, so I think using
> the same name here is better than leaving the catchy
> sock_create_kern() error-prone.
Ok.
Powered by blists - more mailing lists