lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 03 Sep 2022 09:40:14 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Paul Durrant <pdurrant@...zon.com> Cc: netdev@...r.kernel.org, xen-devel@...ts.xenproject.org, wei.liu@...nel.org, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, marmarek@...isiblethingslab.com Subject: Re: [PATCH net] xen-netback: only remove 'hotplug-status' when the vif is actually destroyed Hello: This patch was applied to netdev/net.git (master) by David S. Miller <davem@...emloft.net>: On Thu, 1 Sep 2022 12:55:54 +0100 you wrote: > Removing 'hotplug-status' in backend_disconnected() means that it will be > removed even in the case that the frontend unilaterally disconnects (which > it is free to do at any time). The consequence of this is that, when the > frontend attempts to re-connect, the backend gets stuck in 'InitWait' > rather than moving straight to 'Connected' (which it can do because the > hotplug script has already run). > Instead, the 'hotplug-status' mode should be removed in netback_remove() > i.e. when the vif really is going away. > > [...] Here is the summary with links: - [net] xen-netback: only remove 'hotplug-status' when the vif is actually destroyed https://git.kernel.org/netdev/net/c/c55f34b6aec2 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists