mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH 1/2] Revert "xen-netback: remove 'hotplug-status' once it has served its purpose"
@ 2022-02-21  3:42 Marek Marczykowski-Górecki
  2022-02-21  3:42 ` [PATCH 2/2] Revert "xen-netback: Check for hotplug-status existence before watching" Marek Marczykowski-Górecki
  2022-02-21  9:10 ` [PATCH 1/2] Revert "xen-netback: remove 'hotplug-status' once it has served its purpose" kernel test robot
  0 siblings, 2 replies; 3+ messages in thread
From: Marek Marczykowski-Górecki @ 2022-02-21  3:42 UTC (permalink / raw)
  To: linux-kernel
  Cc: Marek Marczykowski-Górecki, stable, Michael Brown, Wei Liu,
	Paul Durrant, David S. Miller, Jakub Kicinski,
	moderated list:XEN NETWORK BACKEND DRIVER,
	open list:XEN NETWORK BACKEND DRIVER

This reverts commit 1f2565780e9b7218cf92c7630130e82dcc0fe9c2.

The 'hotplug-status' node should not be removed as long as the vif
device remains configured. Otherwise the xen-netback would wait for
re-running the network script even if it was already called (in case of
the frontent re-connecting). But also, it _should_ be removed when the
vif device is destroyed (for example when unbinding the driver) -
otherwise hotplug script would not configure the device whenever it
re-appear.

Moving removal of the 'hotplug-status' node was a workaround for nothing
calling network script after xen-netback module is reloaded. But when
vif interface is re-created (on xen-netback unbind/bind for example),
the script should be called, regardless of who does that - currently
this case is not handled by the toolstack, and requires manual
script call. Keeping hotplug-status=connected to skip the call is wrong
and leads to not configured interface.

More discussion at
https://lore.kernel.org/xen-devel/afedd7cb-a291-e773-8b0d-4db9b291fa98@ipxe.org/T/#u

Cc: stable@vger.kernel.org
Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
---
Cc: Michael Brown <mcb30@ipxe.org>
---
 drivers/net/xen-netback/xenbus.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/xen-netback/xenbus.c b/drivers/net/xen-netback/xenbus.c
index d24b7a7993aa..ce0f3035bee8 100644
--- a/drivers/net/xen-netback/xenbus.c
+++ b/drivers/net/xen-netback/xenbus.c
@@ -256,6 +256,7 @@ static void backend_disconnect(struct backend_info *be)
 		unsigned int queue_index;
 
 		xen_unregister_watchers(vif);
+		xenbus_rm(XBT_NIL, dev->nodename, "hotplug-status");
 #ifdef CONFIG_DEBUG_FS
 		xenvif_debugfs_delif(vif);
 #endif /* CONFIG_DEBUG_FS */
@@ -675,7 +676,6 @@ static void hotplug_status_changed(struct xenbus_watch *watch,
 
 		/* Not interested in this watch anymore. */
 		unregister_hotplug_status_watch(be);
-		xenbus_rm(XBT_NIL, be->dev->nodename, "hotplug-status");
 	}
 	kfree(str);
 }
-- 
2.31.1


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-02-21  9:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-21  3:42 [PATCH 1/2] Revert "xen-netback: remove 'hotplug-status' once it has served its purpose" Marek Marczykowski-Górecki
2022-02-21  3:42 ` [PATCH 2/2] Revert "xen-netback: Check for hotplug-status existence before watching" Marek Marczykowski-Górecki
2022-02-21  9:10 ` [PATCH 1/2] Revert "xen-netback: remove 'hotplug-status' once it has served its purpose" kernel test robot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®