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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/