From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.citrix.com ([66.165.176.89]:11858 "EHLO SMTP.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754123Ab2JRKCd (ORCPT ); Thu, 18 Oct 2012 06:02:33 -0400 Message-ID: <507FD39F.4060601@citrix.com> Date: Thu, 18 Oct 2012 11:02:07 +0100 From: David Vrabel MIME-Version: 1.0 To: "xen-devel@lists.xensource.com" , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "David S. Miller" , Jens Axboe , , Bjorn Helgaas , , Florian Tobias Schandinat , , Dmitry Torokhov CC: David Vrabel Subject: [PATCH 0/5] drivers: xen frontend devices should handle missed backend CLOSING Content-Type: text/plain; charset="ISO-8859-1" Sender: linux-pci-owner@vger.kernel.org List-ID: 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