From: Anthony PERARD <anthony.perard@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] xen-bus: check whether the frontend is active during device reset...
Date: Wed, 11 Sep 2019 10:04:51 +0100 [thread overview]
Message-ID: <20190911090451.GA1308@perard.uk.xensource.com> (raw)
In-Reply-To: <20190910171753.3775-1-paul.durrant@citrix.com>
On Tue, Sep 10, 2019 at 06:17:53PM +0100, Paul Durrant wrote:
> ...not the backend
>
> Commit cb323146 "xen-bus: Fix backend state transition on device reset"
> contained a subtle mistake. The hunk
>
> @@ -539,11 +556,11 @@ static void xen_device_backend_changed(void *opaque)
>
> /*
> * If the toolstack (or unplug request callback) has set the backend
> - * state to Closing, but there is no active frontend (i.e. the
> - * state is not Connected) then set the backend state to Closed.
> + * state to Closing, but there is no active frontend then set the
> + * backend state to Closed.
> */
> if (xendev->backend_state == XenbusStateClosing &&
> - xendev->frontend_state != XenbusStateConnected) {
> + !xen_device_state_is_active(state)) {
> xen_device_backend_set_state(xendev, XenbusStateClosed);
> }
>
> mistakenly replaced the check of 'xendev->frontend_state' with a check
> (now in a helper function) of 'state', which actually equates to
> 'xendev->backend_state'.
>
> This patch fixes the mistake.
>
> Fixes: cb3231460747552d70af9d546dc53d8195bcb796
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
Thanks,
--
Anthony PERARD
prev parent reply other threads:[~2019-09-11 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 17:17 [Qemu-devel] [PATCH] xen-bus: check whether the frontend is active during device reset Paul Durrant
2019-09-11 9:04 ` Anthony PERARD [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190911090451.GA1308@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).