From: Paolo Bonzini <pbonzini@redhat.com>
To: Ilya Lesokhin <ilyal@mellanox.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Haggai Eran <haggaie@mellanox.com>, Knut Omang <knut.omang@oracle.com>
Subject: Re: [Qemu-devel] Possible reference leak in device_set_realized(...)
Date: Fri, 1 Jan 2016 23:37:35 +0100 [thread overview]
Message-ID: <5686FFAF.3070205@redhat.com> (raw)
In-Reply-To: <VI1PR05MB111929067D12C8996C291CFDD4FE0@VI1PR05MB1119.eurprd05.prod.outlook.com>
On 31/12/2015 19:13, Ilya Lesokhin wrote:
> I was able to overcome this issue by calling object_unparent on my
> device but I’m not sure that the correct way of fixing it.
Yes, it's definitely the right way to fix it.
Paolo
next prev parent reply other threads:[~2016-01-01 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 18:13 [Qemu-devel] Possible reference leak in device_set_realized(...) Ilya Lesokhin
2016-01-01 22:37 ` Paolo Bonzini [this message]
2016-01-12 10:44 ` Knut Omang
2016-01-12 12:00 ` Paolo Bonzini
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=5686FFAF.3070205@redhat.com \
--to=pbonzini@redhat.com \
--cc=haggaie@mellanox.com \
--cc=ilyal@mellanox.com \
--cc=knut.omang@oracle.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).