From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Ma, Stephen B." <stephen.ma@hp.com>,
"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Fix for qemu crash on assertion error when adding PCI passthru device.
Date: Mon, 18 Jun 2012 08:24:33 +0200 [thread overview]
Message-ID: <4FDEC9A1.4070508@web.de> (raw)
In-Reply-To: <4FDDE974.3040001@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On 2012-06-17 16:28, Anthony Liguori wrote:
> On 06/17/2012 03:34 AM, Michael S. Tsirkin wrote:
>> On Sun, Jun 17, 2012 at 06:26:33AM +0000, Ma, Stephen B. wrote:
>>>
>>> Michael,
>>>
>>> Thanks for the review. I added the unparent to the qdev_free.
>>>
>>>
>>> ---
>>> hw/qdev.c | 1 +
>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/hw/qdev.c b/hw/qdev.c
>>> index d2dc28b..ed1328d 100644
>>> --- a/hw/qdev.c
>>> +++ b/hw/qdev.c
>>> @@ -264,6 +264,7 @@ void qdev_init_nofail(DeviceState *dev)
>>> /* Unlink device from bus and free the structure. */
>>> void qdev_free(DeviceState *dev)
>>> {
>>> + object_unparent(OBJECT(dev));
>>> object_delete(OBJECT(dev));
>>> }
>>>
>>> --
>>> 1.7.1
>>
>> Anthony, any feedback?
>
> Yes, this is wrong.
>
> PCI passthrough isn't in qemu.git so it's not clear to me where this is
> happening. Why would qdev_free be called when adding a PCI passthru
> device?
The bug is reproducible with any in-tree device (at least PCI) that
happens to return != 0 from its init handler.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-06-18 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 4:31 [Qemu-devel] [PATCH] Fix for qemu crash on assertion error when adding PCI passthru device Ma, Stephen B.
2012-06-12 8:26 ` Michael S. Tsirkin
2012-06-17 6:26 ` Ma, Stephen B.
2012-06-17 8:34 ` Michael S. Tsirkin
2012-06-17 14:28 ` Anthony Liguori
2012-06-18 6:24 ` Jan Kiszka [this message]
2012-07-18 20:42 ` Ma, Stephen B.
2012-07-19 6:27 ` Jan Kiszka
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=4FDEC9A1.4070508@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stephen.ma@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.