From: David Vrabel <david.vrabel@citrix.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jens Axboe <axboe@kernel.dk>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-fbdev@vger.kernel.org,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: David Vrabel <david.vrabel@citrix.com>
Subject: [PATCH 0/5] drivers: xen frontend devices should handle missed backend CLOSING
Date: Thu, 18 Oct 2012 10:02:07 +0000 [thread overview]
Message-ID: <507FD39F.4060601@citrix.com> (raw)
Subsystem maintainers, you can either pick up the relevant driver patch
or ack it to go via Konrad's Xen tree.
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.
David
next reply other threads:[~2012-10-18 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:02 David Vrabel [this message]
2012-10-18 10:03 ` [PATCH 4/5] xen-fbfront: handle backend CLOSED without CLOSING David Vrabel
2012-10-19 13:00 ` Konrad Rzeszutek Wilk
2012-10-23 4:50 ` Florian Tobias Schandinat
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=507FD39F.4060601@citrix.com \
--to=david.vrabel@citrix.com \
--cc=FlorianSchandinat@gmx.de \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@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).