qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Serge E. Hallyn" <serge@hallyn.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] assert and crash on hot-unplug
Date: Fri, 21 Sep 2012 07:52:42 -0500	[thread overview]
Message-ID: <87392b8rmt.fsf@codemonkey.ws> (raw)
In-Reply-To: <20120920170005.GA25890@mail.hallyn.com>

"Serge E. Hallyn" <serge@hallyn.com> writes:

Hi Serge,

> Hi,
>
> a regression test of CVE-2011-1751 (fixed by
> 505597e4476a6bc219d0ec1362b760d71cb4fdca) found that when writing 2 to
> 0xae08, qemu-system-i386 crashes with
>
> ERROR:qom/object.c:386:object_finalize: assertion failed: (obj->ref == 0)
>
> A simple way to reproduce this (in qemu 1.1 or 1.2) is:
>
> serge@ubuntu:~/qa-regression-testing/scripts$ ~/src/qemu/i386-softmmu/qemu-system-i386 -usb -monitor stdio -vnc :1 -hda x.img
> QEMU 1.2.50 monitor - type 'help' for more information
> (qemu) o 0xae08 2
> **
> ERROR:qom/object.c:386:object_finalize: assertion failed: (obj->ref == 0)
> Aborted (core dumped)
>
> I don't think it's a regression of the CVE, as some added printfs show it is
> the usb controller which is being unplugged (dev 1, fn 2, not dev 1 fn 3).
>
>   Bus  0, device   1, function 2:
>     USB controller: PCI device 8086:7020
>       IRQ 11.
>       BAR4: I/O at 0xc040 [0xc05f].
>       id ""
>   Bus  0, device   1, function 3:
>     Bridge: PCI device 8086:7113
>       IRQ 9.
>       id ""

Thanks, I'll take a look.

Regards,

Anthony Liguori

>
>
> -serge

      reply	other threads:[~2012-09-21 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 17:00 [Qemu-devel] assert and crash on hot-unplug Serge E. Hallyn
2012-09-21 12:52 ` Anthony Liguori [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=87392b8rmt.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=serge@hallyn.com \
    /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).