-----Original Message----- From: Eric Dumazet edumazet@google.com Sent: Tuesday, July 22, 2025 2:52 AM To: Haiyang Zhang haiyangz@linux.microsoft.com Cc: linux-hyperv@vger.kernel.org; netdev@vger.kernel.org; Haiyang Zhang haiyangz@microsoft.com; KY Srinivasan kys@microsoft.com; wei.liu@kernel.org; kuba@kernel.org; pabeni@redhat.com; horms@kernel.org; davem@davemloft.net; sdf@fomichev.me; kuniyu@google.com; ahmed.zaki@intel.com; aleksander.lobakin@intel.com; linux- kernel@vger.kernel.org; stable@vger.kernel.org; #@linux.microsoft.com; 5.4+@linux.microsoft.com Subject: [EXTERNAL] Re: [PATCH net] net: core: Fix the loop in default_device_exit_net()
On Fri, Jul 18, 2025 at 1:21 PM Haiyang Zhang haiyangz@linux.microsoft.com wrote:
From: Haiyang Zhang haiyangz@microsoft.com
The loop in default_device_exit_net() won't be able to properly detect
the
head then stop, and will hit NULL pointer, when a driver, like
hv_netvsc,
automatically moves the slave device together with the master device.
To fix this, add a helper function to return the first migratable netdev correctly, no matter one or two devices were removed from this net's
list
in the last iteration.
Cc: stable@vger.kernel.org # 5.4+
We (network maintainers) prefer a Fixes: tag, so that we can look at the blamed patch, rather than trusting your '5.4' hint.
Without a Fixes tag, you are forcing each reviewer to do the archeology work, and possibly completely miss your point.
Thanks. I will have the Fixes tag in the new patch.
- Haiyang