From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] xen: frontend devices should handle missed backend CLOSING
Date: Fri, 21 Sep 2012 13:10:13 -0400 [thread overview]
Message-ID: <20120921171013.GA9201@phenom.dumpdata.com> (raw)
In-Reply-To: <1348243464-15903-1-git-send-email-david.vrabel@citrix.com>
On Fri, Sep 21, 2012 at 05:04:18PM +0100, David Vrabel wrote:
> The series makes all the Xen frontend drivers handle the backend
> transitioning to CLOSED without the frontend having previously seen
> the backend in the CLOSING state.
>
> Backends shouldn't do this but some do. e.g., if the host is
> XenServer and the toolstack decides to do a forced shutdown of a VBD,
> then the blkfront may miss the CLOSING transition and the /dev/xvdX
> device will not be destroyed which prevents it being reused.
>
> I have seen systems that ended up in this state but it's not clear if
> this was the actual cause. However, I think in general it's a good
> thing to thing to improve the handling of unexpected state
> transitions.
>
> Konrad, I've split this into a patch per frontend in case each patch
> should go via a different maintainer. But if you'd prefer, I can roll
> this up into one patch to via your Xen tree.
I like the split-up. Can you repost them with the different maintainers
CC (scripts/get_maintainers.pl) and with Acked-by from me on them?
>
> David
prev parent reply other threads:[~2012-09-21 17:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 16:04 [PATCH 0/6] xen: frontend devices should handle missed backend CLOSING David Vrabel
2012-09-21 16:04 ` [PATCH 1/6] xen-netfront: handle backend CLOSED without CLOSING David Vrabel
2012-09-21 16:04 ` [PATCH 2/6] xen-blkfront: " David Vrabel
2012-09-25 17:53 ` David Vrabel
2012-10-01 17:19 ` David Vrabel
2012-10-02 20:02 ` Konrad Rzeszutek Wilk
2012-10-05 11:42 ` David Vrabel
2012-10-05 11:55 ` Jan Beulich
2012-10-05 15:57 ` David Vrabel
2012-10-09 16:30 ` Konrad Rzeszutek Wilk
2012-10-04 10:14 ` [Xen-devel] " Jan Beulich
2012-10-04 10:31 ` David Vrabel
2012-09-21 16:04 ` [PATCH 3/6] xen-pcifront: " David Vrabel
2012-09-21 16:04 ` [PATCH 4/6] xen-fbfront: " David Vrabel
2012-09-21 16:04 ` [PATCH 5/6] xen-kbdfront: " David Vrabel
2012-09-21 16:04 ` [PATCH 6/6] xen/hvc: " David Vrabel
2012-09-21 17:10 ` Konrad Rzeszutek Wilk [this message]
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=20120921171013.GA9201@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).