[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<SJ2PR21MB40137E181C23C6550604334BCA5FA@SJ2PR21MB4013.namprd21.prod.outlook.com>
Date: Wed, 23 Jul 2025 20:49:31 +0000
From: Haiyang Zhang <haiyangz@...rosoft.com>
To: Jakub Kicinski <kuba@...nel.org>, Haiyang Zhang
<haiyangz@...ux.microsoft.com>
CC: "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>, KY Srinivasan
<kys@...rosoft.com>, "wei.liu@...nel.org" <wei.liu@...nel.org>, Dexuan Cui
<decui@...rosoft.com>, "andrew+netdev@...n.ch" <andrew+netdev@...n.ch>,
"sd@...asysnail.net" <sd@...asysnail.net>, "viro@...iv.linux.org.uk"
<viro@...iv.linux.org.uk>, "chuck.lever@...cle.com" <chuck.lever@...cle.com>,
"neil@...wn.name" <neil@...wn.name>, "edumazet@...gle.com"
<edumazet@...gle.com>, "pabeni@...hat.com" <pabeni@...hat.com>,
"horms@...nel.org" <horms@...nel.org>, "davem@...emloft.net"
<davem@...emloft.net>, "kuniyu@...gle.com" <kuniyu@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [EXTERNAL] Re: [PATCH net, 0/2] net: Add llist_node init and fix
hv_netvsc namespace error
> -----Original Message-----
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Tuesday, July 22, 2025 9:45 PM
> To: Haiyang Zhang <haiyangz@...ux.microsoft.com>
> Cc: linux-hyperv@...r.kernel.org; netdev@...r.kernel.org; Haiyang Zhang
> <haiyangz@...rosoft.com>; KY Srinivasan <kys@...rosoft.com>;
> wei.liu@...nel.org; Dexuan Cui <decui@...rosoft.com>;
> andrew+netdev@...n.ch; sd@...asysnail.net; viro@...iv.linux.org.uk;
> chuck.lever@...cle.com; neil@...wn.name; edumazet@...gle.com;
> pabeni@...hat.com; horms@...nel.org; davem@...emloft.net;
> kuniyu@...gle.com; linux-kernel@...r.kernel.org
> Subject: [EXTERNAL] Re: [PATCH net, 0/2] net: Add llist_node init and fix
> hv_netvsc namespace error
>
> On Tue, 22 Jul 2025 16:50:46 -0700 Haiyang Zhang wrote:
> > Add llist_node init to setup_net(), so we can check if the node is on
> list.
> > Then, fix the namespace callback function in hv_netvsc.
>
> Can you not do the moving from a workqueue? Schedule a work, let the
> stack finish what it's doing, take rtnl_lock, do you your own moving?
Thanks for the suggestion! I will implement and test it.
- Haiyang
Powered by blists - more mailing lists