From: Guenter Roeck <linux@roeck-us.net>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Guenter Roeck" <linux@roeck-us.net>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] [PATCH] ehci: Ensure that device is not NULL before calling usb_ep_get
Date: Tue, 30 Jul 2019 10:45:10 -0700 [thread overview]
Message-ID: <1564508710-22909-1-git-send-email-linux@roeck-us.net> (raw)
The following assert is seen once in a while while resetting the
Linux kernel.
qemu-system-x86_64: hw/usb/core.c:734: usb_ep_get:
Assertion `dev != NULL' failed.
The call to usb_ep_get() originates from ehci_execute().
Analysis and debugging shows that p->queue->dev can indeed be NULL
in this function. Add check for this condition and return an error
if it is seen.
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
hw/usb/hcd-ehci.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/hw/usb/hcd-ehci.c b/hw/usb/hcd-ehci.c
index 62dab05..c759f3e 100644
--- a/hw/usb/hcd-ehci.c
+++ b/hw/usb/hcd-ehci.c
@@ -1348,6 +1348,11 @@ static int ehci_execute(EHCIPacket *p, const char *action)
return -1;
}
+ if (p->queue->dev == NULL) {
+ ehci_trace_guest_bug(p->queue->ehci, "No device attached to queue\n");
+ return -1;
+ }
+
if (get_field(p->qtd.token, QTD_TOKEN_TBYTES) > BUFF_SIZE) {
ehci_trace_guest_bug(p->queue->ehci,
"guest requested more bytes than allowed");
--
2.7.4
next reply other threads:[~2019-07-30 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 17:45 Guenter Roeck [this message]
2019-07-31 11:08 ` [Qemu-devel] [PATCH] ehci: Ensure that device is not NULL before calling usb_ep_get Philippe Mathieu-Daudé
2019-07-31 21:11 ` Guenter Roeck
2019-08-02 14:11 ` Gerd Hoffmann
2019-08-02 16:46 ` Guenter Roeck
2019-08-02 17:28 ` Guenter Roeck
2019-08-06 13:23 ` Guenter Roeck
2019-08-13 11:42 ` Gerd Hoffmann
2019-08-14 14:41 ` Guenter Roeck
2019-08-20 15:38 ` Guenter Roeck
2019-08-21 8:54 ` Gerd Hoffmann
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=1564508710-22909-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@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).