All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, afaerber@suse.de, 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 18:23:24 +0800	[thread overview]
Message-ID: <20140217102324.GA1925@amosk.info> (raw)
In-Reply-To: <1388624531-13439-1-git-send-email-akong@redhat.com>

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?

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
> 

  parent reply	other threads:[~2014-02-17 10:23 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 [this message]
2014-02-17 11:44   ` Andreas Färber

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=20140217102324.GA1925@amosk.info \
    --to=akong@redhat.com \
    --cc=afaerber@suse.de \
    --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 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.