On Wed, Sep 18, 2019 at 12:57:02PM +0100, Paul Durrant wrote: > When a frontend gracefully disconnects from an offline backend, it will > set its own state to XenbusStateClosed. The code in xen-block.c correctly > deals with this and sets the backend into XenbusStateClosed. Unfortunately > it is possible for toolstack to actually delete the frontend area > before the state key has been read, leading to an apparent frontend state > of XenbusStateUnknown. This prevents the backend state from transitioning > to XenbusStateClosed and hence leaves it limbo. > > This patch simply treats a frontend state of XenbusStateUnknown the same > as XenbusStateClosed, which will unblock the backend in these circumstances. > > Reported-by: Mark Syms <mark.s...@citrix.com> > Signed-off-by: Paul Durrant <paul.durr...@citrix.com>
Acked-by: Anthony PERARD <anthony.per...@citrix.com> Thanks, -- Anthony PERARD _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
