[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] xen-block: treat XenbusStateUnknown the same as XenbusStateC
From: |
Anthony PERARD |
Subject: |
Re: [PATCH] xen-block: treat XenbusStateUnknown the same as XenbusStateClosed |
Date: |
Mon, 23 Sep 2019 12:34:15 +0100 |
User-agent: |
Mutt/1.12.2 (2019-09-21) |
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 <address@hidden>
> Signed-off-by: Paul Durrant <address@hidden>
Acked-by: Anthony PERARD <address@hidden>
Thanks,
--
Anthony PERARD