qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Cc: famz@redhat.com, jsnow@redhat.com, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qdev: Fix use after free in qdev_init_nofail error path
Date: Tue, 2 Aug 2016 18:55:13 +0200	[thread overview]
Message-ID: <e9528ff7-6644-a507-673a-a21ce5b4797e@redhat.com> (raw)
In-Reply-To: <1470134960-87851-1-git-send-email-imammedo@redhat.com>



On 02/08/2016 12:49, Igor Mammedov wrote:
> Since 69382d8b (qdev: Fix object reference leak in case device.realize()
> fails), object_property_set_bool releases the device object
> in case realize's failed and device hasn't explicitly assigned
> parent. It happens due to object_unparent() on error handling
> path releases not only implicitly set parent but also calls
> device_unparent() which releases the remaining reference hold
> buy parent bus.
> 
> qdev_try_create() created device has only 1 reference hold by
> parent bus which makes impossible to unparent/re-parent object
> without destroying it.
> 
> Fix it by making caller of qdev_try_create()/qdev_init_nofail()
> own a reference from object_new() until qdev_init_nofail() is
> successfully executed so that uparenting won't destroy device
> until caller owns pointer returned by qdev_try_create().

Your patch is indeed nicer in theory, but in practice I'm not sure that
there are no occurrences of object_new + qdev_init_nofail, or
qdev_try_create + object_property_set_bool.  These would be broken, so
I'm going with Fam's.

Paolo

> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> ---
>  hw/core/qdev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
> index ee4a083..0139d67 100644
> --- a/hw/core/qdev.c
> +++ b/hw/core/qdev.c
> @@ -151,7 +151,6 @@ DeviceState *qdev_try_create(BusState *bus, const char *type)
>      }
>  
>      qdev_set_parent_bus(dev, bus);
> -    object_unref(OBJECT(dev));
>      return dev;
>  }
>  
> @@ -360,6 +359,7 @@ void qdev_init_nofail(DeviceState *dev)
>                            object_get_typename(OBJECT(dev)));
>          exit(1);
>      }
> +    object_unref(OBJECT(dev));
>  }
>  
>  void qdev_machine_creation_done(void)
> 

      reply	other threads:[~2016-08-02 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 10:49 [Qemu-devel] [PATCH v2] qdev: Fix use after free in qdev_init_nofail error path Igor Mammedov
2016-08-02 16:55 ` Paolo Bonzini [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=e9528ff7-6644-a507-673a-a21ce5b4797e@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=famz@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jsnow@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).