qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Amos Kong <akong@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, aliguori@amazon.com, hutao@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v2] qdev: add the device to the QOM tree before using it to set a link
Date: Mon, 17 Feb 2014 12:44:34 +0100	[thread overview]
Message-ID: <5301F622.4000609@suse.de> (raw)
In-Reply-To: <20140217102324.GA1925@amosk.info>

Am 17.02.2014 11:23, schrieb Amos Kong:
> On Thu, Jan 02, 2014 at 09:02:11AM +0800, Amos Kong wrote:
>> Test steps:
>>   (qemu) device_add e1000,addr=adsf
>>   Property 'e1000.addr' doesn't take value 'adsf'
>>   (qemu) info qtree
>> Then qemu crashed.
>>
>> Currently we set a link to the new device for qdev parent bus, but the
>> device hasn't been added to QOM tree. When it fails to set properties,
>> object_unparent() can't cleanup the device.
>>
>> This patch moves qdev_set_parent_bus() back to object_property_add_child(),
>> we only needs to unref the object if setting properties fails.
>>
>> Signed-off-by: Amos Kong <akong@redhat.com>
>> ---
>> V2: fix bz by adjust the initialization order (Paolo)
> 
> Hi Anthony, other maintainer
> 
> The V2 already reviewed and tested by Markus. Can you help to review & apply it?

Amos, I had pointed out to Paolo (IRC?) that this differs from how all
legacy devices are being created, so I consider it a bad idea.
qdev_set_parent_bus() is called from qdev_try_create(), which is called
by qdev_create(). Devices may thus assume that the bus is set early,
e.g. in their property setters invoked by qemu_opt_foreach(), and some
functions have special behavior for a NULL bus (thinking of ISA here),
so the change may lead to silent functional changes.

Long-term we will have to move the code adding the device out of realize
because we want to make realize work recursively on the composition
tree. So what about rather moving the code adding the device to
periph-anon / periph between dev->id and qemu_opt_foreach() so that the
original unparenting works as expected?

Regards,
Andreas

> 
> Thanks, Amos
> 
>> ---
>>  qdev-monitor.c | 10 +++++-----
>>  1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/qdev-monitor.c b/qdev-monitor.c
>> index dc37a43..4070b0a 100644
>> --- a/qdev-monitor.c
>> +++ b/qdev-monitor.c
>> @@ -518,16 +518,11 @@ DeviceState *qdev_device_add(QemuOpts *opts)
>>      /* create device, set properties */
>>      dev = DEVICE(object_new(driver));
>>  
>> -    if (bus) {
>> -        qdev_set_parent_bus(dev, bus);
>> -    }
>> -
>>      id = qemu_opts_id(opts);
>>      if (id) {
>>          dev->id = id;
>>      }
>>      if (qemu_opt_foreach(opts, set_property, dev, 1) != 0) {
>> -        object_unparent(OBJECT(dev));
>>          object_unref(OBJECT(dev));
>>          return NULL;
>>      }
>> @@ -541,6 +536,11 @@ DeviceState *qdev_device_add(QemuOpts *opts)
>>                                    OBJECT(dev), NULL);
>>          g_free(name);
>>      }
>> +
>> +    if (bus) {
>> +        qdev_set_parent_bus(dev, bus);
>> +    }
>> +
>>      object_property_set_bool(OBJECT(dev), true, "realized", &err);
>>      if (err != NULL) {
>>          qerror_report_err(err);
>> -- 
>> 1.8.4.2
>>


-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2014-02-17 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02  1:02 [Qemu-devel] [PATCH v2] qdev: add the device to the QOM tree before using it to set a link Amos Kong
2014-01-20 12:47 ` Paolo Bonzini
2014-01-20 13:12 ` Markus Armbruster
2014-02-17 10:23 ` Amos Kong
2014-02-17 11:44   ` Andreas Färber [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=5301F622.4000609@suse.de \
    --to=afaerber@suse.de \
    --cc=akong@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=hutao@cn.fujitsu.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).