From: Igor Mammedov <imammedo@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU device refcounting when device creates a container MR
Date: Thu, 10 Mar 2022 17:30:53 +0100 [thread overview]
Message-ID: <20220310173053.5eb97f20@redhat.com> (raw)
In-Reply-To: <CAFEAcA8Nvr-7QYHv2-K+zN37i=ZXa8_Skb53PaTJzSdhXaBq3g@mail.gmail.com>
Do On Thu, 10 Mar 2022 16:05:24 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> On Thu, 10 Mar 2022 at 15:36, Igor Mammedov <imammedo@redhat.com> wrote:
> >
> > On Wed, 9 Mar 2022 16:56:21 +0000
> > Peter Maydell <peter.maydell@linaro.org> wrote:
> > > ...also, in the device-introspect-test where I see this problem,
> > > unrealize is never going to be called anyway, because the device
> > > is only put through "instance_init" and then dereffed (which
> > > does not result in instance_finalize being called, because the
> > > refcount is still non-zero).
> >
> > question is why introspected device is deferred instead of being
> > destroyed if it's no longer needed?
>
> ...because the reference count is not zero.
>
> What is supposed to happen is:
> * device is created (inited), and has refcount of 1
> * introspection code does its thing
> * introspection code derefs the device, and it gets deinited
>
> This bug means that when the device is inited it has a refcount
> that is too high, and so despite the code that creates it
> correctly dereffing it, it's still lying around.
looks like ref count leak somewhere, instance_finalize() take care
of cleaning up instance_init() actions.
Do you have an example/reproducer?
> thanks
> -- PMM
>
next prev parent reply other threads:[~2022-03-10 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 10:33 QEMU device refcounting when device creates a container MR Peter Maydell
2022-03-09 10:40 ` Philippe Mathieu-Daudé
2022-03-10 13:19 ` Peter Xu
2022-03-10 13:45 ` Peter Maydell
2022-03-11 2:19 ` Peter Xu
2022-03-09 16:21 ` Paolo Bonzini
2022-03-09 16:53 ` Peter Maydell
2022-03-09 16:56 ` Peter Maydell
2022-03-10 15:36 ` Igor Mammedov
2022-03-10 16:05 ` Peter Maydell
2022-03-10 16:30 ` Igor Mammedov [this message]
2022-03-10 17:11 ` Peter Maydell
2022-03-18 17:13 ` Igor Mammedov
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=20220310173053.5eb97f20@redhat.com \
--to=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.