From: Jakub Kicinski <kuba@kernel.org>
To: Haiyang Zhang <haiyangz@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
haiyangz@microsoft.com, kys@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, andrew+netdev@lunn.ch, sd@queasysnail.net,
viro@zeniv.linux.org.uk, chuck.lever@oracle.com, neil@brown.name,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
davem@davemloft.net, kuniyu@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net, 0/2] net: Add llist_node init and fix hv_netvsc namespace error
Date: Tue, 22 Jul 2025 18:44:33 -0700 [thread overview]
Message-ID: <20250722184433.2b951171@kernel.org> (raw)
In-Reply-To: <1753228248-20865-1-git-send-email-haiyangz@linux.microsoft.com>
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?
--
pw-bot: cr
next prev parent reply other threads:[~2025-07-23 1:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 23:50 [PATCH net, 0/2] net: Add llist_node init and fix hv_netvsc namespace error Haiyang Zhang
2025-07-22 23:50 ` [PATCH net, 1/2] net: core: Fix missing init of llist_node in setup_net() Haiyang Zhang
2025-07-23 0:01 ` Kuniyuki Iwashima
2025-07-23 0:17 ` [EXTERNAL] " Haiyang Zhang
2025-07-22 23:50 ` [PATCH net, 2/2] hv_netvsc: Fix panic during namespace deletion with VF Haiyang Zhang
2025-07-23 1:44 ` Jakub Kicinski [this message]
2025-07-23 20:49 ` [EXTERNAL] Re: [PATCH net, 0/2] net: Add llist_node init and fix hv_netvsc namespace error Haiyang Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250722184433.2b951171@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=kuniyu@google.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=viro@zeniv.linux.org.uk \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).