From: Markus Armbruster <armbru@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] device_add error handling regressed in v1.5.0
Date: Mon, 20 Jan 2014 14:10:18 +0100 [thread overview]
Message-ID: <87txcyu7d1.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <87d2jmx1ti.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Mon, 20 Jan 2014 13:41:45 +0100")
Markus Armbruster <armbru@redhat.com> writes:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> Il 17/01/2014 11:23, Markus Armbruster ha scritto:
>>> Watch this:
>>>
>>> $ upstream-qemu -nodefaults -S -display none -monitor stdio
>>> QEMU 1.7.50 monitor - type 'help' for more information
>>> (qemu) device_add e1000,netdev=xxx
>>> Property 'e1000.netdev' can't find value 'xxx'
>>> (qemu) info qtree
> [...]
>>> Segmentation fault (core dumped)
>>>
>>> Even though device_add failed, it still created a node in the qtree!
>>>
>>> Same issue observed with scsi-hd. Looks like a qdev problem, not a
>>> device problem.
>>>
>>> git-bisect blames this one:
>>>
>>> e0a83fc2c1582dc8d4453849852ebe6c258b7c3a is the first bad commit
>>> commit e0a83fc2c1582dc8d4453849852ebe6c258b7c3a
>>> Author: Paolo Bonzini <pbonzini@redhat.com>
>>> Date: Tue Apr 2 15:50:00 2013 +0200
>>>
>>> qom: do nothing on unparent of object without parent
>>>
>>> Otherwise, device_unparent will fail to get a canonical path of
>>> the object.
>>>
>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>> Message-id: 1364910600-3418-1-git-send-email-pbonzini@redhat.com
>>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>>>
>>
>> I think Amos had a fix for this.
>
> Amos, do you?
Found it: "[PATCH v2] qdev: add the device to the QOM tree before using
it to set a link" seems to fix it.
prev parent reply other threads:[~2014-01-20 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 10:23 [Qemu-devel] device_add error handling regressed in v1.5.0 Markus Armbruster
2014-01-17 12:41 ` Paolo Bonzini
2014-01-20 12:41 ` Markus Armbruster
2014-01-20 13:10 ` Markus Armbruster [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=87txcyu7d1.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=afaerber@suse.de \
--cc=akong@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 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.