From: Stefan Hajnoczi <stefanha@redhat.com>
To: Gonglei <arei.gonglei@hotmail.com>
Cc: 'Stefan Hajnoczi' <stefanha@gmail.com>,
arei.gonglei@huawei.com, weidong.huang@huawei.com,
qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in transports
Date: Fri, 5 Sep 2014 17:28:24 +0100 [thread overview]
Message-ID: <20140905162824.GA12242@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <BLU437-SMTP73400A494E41C51FDBE7999FC20@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Fri, Sep 05, 2014 at 11:46:32PM +0800, Gonglei wrote:
> Hi,
>
> > Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in
> > transports
> >
> > On Thu, Sep 04, 2014 at 07:41:32PM +0800, arei.gonglei@huawei.com wrote:
> > > From: Gonglei <arei.gonglei@huawei.com>
> > >
> > > object_initialize() leaves the object with a refcount of 1.
> > > object_property_add_child() adds its own reference which is dropped
> > > again when the property is deleted.
> > >
> > > The upshot of this is that we always have a refcount >= 1. Upon hot
> > > unplug the virtio-net child is not finalized!
> > >
> > > Drop our reference after the child property has been added to the
> > > parent.
> > >
> > > Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> > > ---
> > > Stefan had post virtio-blk in commit c5d49db4, but virtio-net has
> > > the same problem. Maybe the other virtio devices have too.
> > > ---
> > > hw/virtio/virtio-pci.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > > index ddb5da1..78dcd68 100644
> > > --- a/hw/virtio/virtio-pci.c
> > > +++ b/hw/virtio/virtio-pci.c
> > > @@ -1456,6 +1456,7 @@ static void virtio_net_pci_instance_init(Object
> > *obj)
> > > VirtIONetPCI *dev = VIRTIO_NET_PCI(obj);
> > > object_initialize(&dev->vdev, sizeof(dev->vdev), TYPE_VIRTIO_NET);
> > > object_property_add_child(obj, "virtio-backend", OBJECT(&dev->vdev),
> > NULL);
> > > + object_unref(OBJECT(&dev->vdev));
> > > }
> > >
> > > static const TypeInfo virtio_net_pci_info = {
> >
> > You just copied my commit but didn't consider all the work I did before
> > to make virtio-blk safe. Similar work is necessary for virtio-net.
> >
> > Before it is okay to finalize the virtio-net (dev->vdev) object,
>
> Sorry? In my case the virtio-net object will not be finalized at present
> because its obj->ref is non-1 when we hot-unplug a virtio-net-pci device.
"Before" refers to making virtio-pci/virtio-net fixes first and then
object_unref() second. It does not mean "previously" here.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-05 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 11:41 [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in transports arei.gonglei
2014-09-05 9:08 ` Gonglei (Arei)
2014-09-05 10:32 ` Michael S. Tsirkin
2014-09-05 15:46 ` Gonglei
2014-09-05 12:10 ` Stefan Hajnoczi
2014-09-05 15:46 ` Gonglei
2014-09-05 16:28 ` Stefan Hajnoczi [this message]
2014-09-08 12:47 ` Gonglei
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=20140905162824.GA12242@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=arei.gonglei@hotmail.com \
--cc=arei.gonglei@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=weidong.huang@huawei.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 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).