From: Bastian Blank <bastian@waldi.eu.org>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: netdev@vger.kernel.org, Ian Campbell <ian.campbell@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH net-next v2 2/2] xen-netback: handle frontends that fail to transition through Closing
Date: Fri, 20 Sep 2013 18:14:31 +0200 [thread overview]
Message-ID: <20130920161431.GA19095@mail.waldi.eu.org> (raw)
In-Reply-To: <1379685460-25032-3-git-send-email-paul.durrant@citrix.com>
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?
Bastian
--
If there are self-made purgatories, then we all have to live in them.
-- Spock, "This Side of Paradise", stardate 3417.7
next prev parent reply other threads:[~2013-09-20 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 13:57 [PATCH net-next 0/2] xen-netback: windows frontend compatibility fixes Paul Durrant
2013-09-20 13:57 ` [PATCH net-next v2 1/2] xen-netback: add a vif-is-connected flag Paul Durrant
2013-09-20 18:40 ` David Miller
2013-09-20 18:40 ` David Miller
2013-09-22 2:56 ` annie li
2013-09-22 2:56 ` [Xen-devel] " annie li
2013-09-23 8:51 ` Paul Durrant
2013-09-23 8:51 ` [Xen-devel] " Paul Durrant
2013-09-20 13:57 ` Paul Durrant
2013-09-20 13:57 ` [PATCH net-next v2 2/2] xen-netback: handle frontends that fail to transition through Closing Paul Durrant
2013-09-20 16:14 ` Bastian Blank [this message]
2013-09-23 8:59 ` Paul Durrant
2013-09-23 8:59 ` [Xen-devel] " Paul Durrant
2013-09-20 13:57 ` Paul Durrant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130920161431.GA19095@mail.waldi.eu.org \
--to=bastian@waldi.eu.org \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.