[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130919.140513.2047786411565716987.davem@davemloft.net>
Date: Thu, 19 Sep 2013 14:05:13 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: paul.durrant@...rix.com
Cc: xen-devel@...ts.xen.org, netdev@...r.kernel.org,
david.vrabel@...rix.com, wei.liu2@...rix.com,
ian.campbell@...rix.com
Subject: Re: [PATCH net-next v4] Don't destroy the netdev until the vif is
shut down
From: Paul Durrant <paul.durrant@...rix.com>
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 <paul.durrant@...rix.com>
I think all of the testing requests have been satisfied so I have
applied this.
But _please_ write a more proper subject line in future patch
submissions. You have to provide a subsystem prefix in the
subject line, here I added "xen-netback: ", otherwise someone
skimming the shortlog has no idea what area of code this change
touches.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists