From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Longpeng(Mike)" <longpeng2@huawei.com>, kraxel@redhat.com
Cc: Gonglei <arei.gonglei@huawei.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] usb/xchi: avoid trigger assertion if guest write wrong epid
Date: Tue, 30 Apr 2019 09:43:58 +0200 [thread overview]
Message-ID: <2faba88e-19a3-2674-afa8-f9cfe8241da9@redhat.com> (raw)
In-Reply-To: <1556605301-44112-1-git-send-email-longpeng2@huawei.com>
On 4/30/19 8:21 AM, Longpeng(Mike) wrote:
> From: Longpeng <longpeng2@huawei.com>
>
> we found the following core in our environment:
> 0 0x00007fc6b06c2237 in raise ()
> 1 0x00007fc6b06c3928 in abort ()
> 2 0x00007fc6b06bb056 in __assert_fail_base ()
> 3 0x00007fc6b06bb102 in __assert_fail ()
> 4 0x0000000000702e36 in xhci_kick_ep (...)
> 5 0x000000000047897a in memory_region_write_accessor (...)
> 6 0x000000000047767f in access_with_adjusted_size (...)
> 7 0x000000000047944d in memory_region_dispatch_write (...)
> (mr=mr@entry=0x7fc6a0138df0, addr=addr@entry=156, data=1648892416,
> size=size@entry=4, attrs=attrs@entry=...)
> 8 0x000000000042df17 in address_space_write_continue (...)
> 10 0x000000000043084d in address_space_rw (...)
> 11 0x000000000047451b in kvm_cpu_exec (cpu=cpu@entry=0x1ab11b0)
> 12 0x000000000045dcf5 in qemu_kvm_cpu_thread_fn (arg=0x1ab11b0)
> 13 0x0000000000870631 in qemu_thread_start (args=args@entry=0x1acfb50)
> 14 0x00000000008959a7 in thread_entry_for_hotfix (pthread_cb=<optimized out>)
> 15 0x00007fc6b0a60dd5 in start_thread ()
> 16 0x00007fc6b078a59d in clone ()
>
> (gdb) f 5
> 5 0x000000000047897a in memory_region_write_accessor (...)
> 529 mr->ops->write(mr->opaque, addr, tmp, size);
> (gdb) p /x tmp
> $9 = 0x62481a00 <-- last byte 0x00 is @epid
>
> xhci_doorbell_write() already check the upper bound of @slotid an @epid,
> it also need to check the lower bound.
>
> Cc: Gonglei <arei.gonglei@huawei.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Longpeng <longpeng2@huawei.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> v1 -> v2:
> 1) update the description, include the full backtrace
> 2) remove unnecessary check: 'reg == 0'
>
> ---
> hw/usb/hcd-xhci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/usb/hcd-xhci.c b/hw/usb/hcd-xhci.c
> index ec28bee..d8472b4 100644
> --- a/hw/usb/hcd-xhci.c
> +++ b/hw/usb/hcd-xhci.c
> @@ -3137,7 +3137,7 @@ static void xhci_doorbell_write(void *ptr, hwaddr reg,
> streamid = (val >> 16) & 0xffff;
> if (reg > xhci->numslots) {
> DPRINTF("xhci: bad doorbell %d\n", (int)reg);
> - } else if (epid > 31) {
> + } else if (epid == 0 || epid > 31) {
> DPRINTF("xhci: bad doorbell %d write: 0x%x\n",
> (int)reg, (uint32_t)val);
> } else {
>
next prev parent reply other threads:[~2019-04-30 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 6:21 [Qemu-devel] [PATCH v2] usb/xchi: avoid trigger assertion if guest write wrong epid Longpeng(Mike)
2019-04-30 6:21 ` Longpeng(Mike)
2019-04-30 7:43 ` Philippe Mathieu-Daudé [this message]
2019-04-30 7:43 ` Philippe Mathieu-Daudé
2019-05-02 0:49 ` no-reply
2019-05-02 0:49 ` no-reply
2019-05-02 6:41 ` Gerd Hoffmann
2019-05-02 6:41 ` 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=2faba88e-19a3-2674-afa8-f9cfe8241da9@redhat.com \
--to=philmd@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=kraxel@redhat.com \
--cc=longpeng2@huawei.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).