From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: dgilbert@redhat.com
Subject: Re: [PATCH] xhci: recheck slot status
Date: Tue, 7 Jan 2020 10:10:46 +0100 [thread overview]
Message-ID: <eb17bf85-5976-8611-91cc-35d2499f2bef@redhat.com> (raw)
In-Reply-To: <20200107083606.12393-1-kraxel@redhat.com>
On 1/7/20 9:36 AM, Gerd Hoffmann wrote:
> Factor out slot status check into a helper function. Add an additional
> check after completing transfers. This is needed in case a guest
> queues multiple transfers in a row and a device unplug happens while
> qemu processes them.
>
> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1786413
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/usb/hcd-xhci.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/hw/usb/hcd-xhci.c b/hw/usb/hcd-xhci.c
> index 80988bb305a1..c198a2d150c9 100644
> --- a/hw/usb/hcd-xhci.c
> +++ b/hw/usb/hcd-xhci.c
> @@ -1861,6 +1861,13 @@ static void xhci_kick_ep(XHCIState *xhci, unsigned int slotid,
> xhci_kick_epctx(epctx, streamid);
> }
>
> +static bool xhci_slot_ok(XHCIState *xhci, int slotid)
> +{
> + return (xhci->slots[slotid - 1].uport &&
> + xhci->slots[slotid - 1].uport->dev &&
> + xhci->slots[slotid - 1].uport->dev->attached);
> +}
> +
> static void xhci_kick_epctx(XHCIEPContext *epctx, unsigned int streamid)
> {
> XHCIState *xhci = epctx->xhci;
> @@ -1878,9 +1885,7 @@ static void xhci_kick_epctx(XHCIEPContext *epctx, unsigned int streamid)
>
> /* If the device has been detached, but the guest has not noticed this
> yet the 2 above checks will succeed, but we must NOT continue */
> - if (!xhci->slots[epctx->slotid - 1].uport ||
> - !xhci->slots[epctx->slotid - 1].uport->dev ||
> - !xhci->slots[epctx->slotid - 1].uport->dev->attached) {
> + if (!xhci_slot_ok(xhci, epctx->slotid)) {
> return;
> }
>
> @@ -1987,6 +1992,10 @@ static void xhci_kick_epctx(XHCIEPContext *epctx, unsigned int streamid)
> } else {
> xhci_fire_transfer(xhci, xfer, epctx);
> }
> + if (!xhci_slot_ok(xhci, epctx->slotid)) {
> + /* surprise removal -> stop processing */
I'd use "unexpected removal", but surprise is funnier :)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> + break;
> + }
> if (xfer->complete) {
> /* update ring dequeue ptr */
> xhci_set_ep_state(xhci, epctx, stctx, epctx->state);
>
prev parent reply other threads:[~2020-01-07 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 8:36 [PATCH] xhci: recheck slot status Gerd Hoffmann
2020-01-07 8:55 ` no-reply
2020-01-07 9:10 ` Philippe Mathieu-Daudé [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=eb17bf85-5976-8611-91cc-35d2499f2bef@redhat.com \
--to=philmd@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).