[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD01103F3@AMSPEX01CL01.citrite.net>
Date: Mon, 23 Sep 2013 08:59:57 +0000
From: Paul Durrant <Paul.Durrant@...rix.com>
To: Bastian Blank <bastian@...di.eu.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>,
Wei Liu <wei.liu2@...rix.com>,
David Vrabel <david.vrabel@...rix.com>,
Ian Campbell <Ian.Campbell@...rix.com>
Subject: RE: [Xen-devel] [PATCH net-next v2 2/2] xen-netback: handle
frontends that fail to transition through Closing
> -----Original Message-----
> From: Bastian Blank [mailto:bastian@...di.eu.org]
> Sent: 20 September 2013 17:15
> To: Paul Durrant
> Cc: netdev@...r.kernel.org; xen-devel@...ts.xen.org; Wei Liu; David Vrabel;
> Ian Campbell
> Subject: Re: [Xen-devel] [PATCH net-next v2 2/2] xen-netback: handle
> frontends that fail to transition through Closing
>
> On Fri, Sep 20, 2013 at 02:57:40PM +0100, Paul Durrant wrote:
> > Some old Windows frontends fail to transition through the xenbus Closing
> > state and move directly from Connected to Closed. Handle this case
> properly.
>
> What happens in this case? Are there other state changes that will do
> unwanted things?
>
Hmm, now you mention it I suspect a transition directly to an unknown state may also not do the right thing. Perhaps it would be better to go straight to a more robust state model as suggested by David Vrabel.
Paul
Powered by blists - more mailing lists