Thread (9 messages) flat view 9 messages, 4 authors, 2013-09-20

Re: [PATCH net-next v4] Don't destroy the netdev until the vif is shut down

From: David Miller <davem@davemloft.net>
Date: 2013-09-18 00:31:04

From: Paul Durrant <redacted>
Date: Tue, 17 Sep 2013 17:46:08 +0100
Without this patch, if a frontend cycles through states Closing
and Closed (which Windows frontends need to do) then the netdev
will be destroyed and requires re-invocation of hotplug scripts
to restore state before the frontend can move to Connected. Thus
when udev is not in use the backend gets stuck in InitWait.

With this patch, the netdev is left alone whilst the backend is
still online and is only de-registered and freed just prior to
destroying the vif (which is also nicely symmetrical with the
netdev allocation and registration being done during probe) so
no re-invocation of hotplug scripts is required.

Signed-off-by: Paul Durrant <redacted>
Can a xen driver expert please review and give an Acked-by:?

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help