xen-blkfront: handle backend CLOSED without CLOSING
authorDavid Vrabel <david.vrabel@citrix.com>
Tue, 4 Feb 2014 18:53:56 +0000 (18:53 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 1 Apr 2014 23:58:50 +0000 (00:58 +0100)
commit93fb7adb880cf960485cfe4c599904e959890be9
tree154cd1a86cdb0c775c9246a7d0c92adc99be798a
parent78f94be0386e7b4d2a871950038b66242ff662db
xen-blkfront: handle backend CLOSED without CLOSING

commit 3661371701e714f0cea4120f6a365340858fb4e4 upstream.

Backend drivers shouldn't transistion to CLOSED unless the frontend is
CLOSED.  If a backend does transition to CLOSED too soon then the
frontend may not see the CLOSING state and will not properly shutdown.

So, treat an unexpected backend CLOSED state the same as CLOSING.

Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/block/xen-blkfront.c