From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51780) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aF8KL-0003hB-Jm for qemu-devel@nongnu.org; Fri, 01 Jan 2016 17:37:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aF8KK-0001RW-UV for qemu-devel@nongnu.org; Fri, 01 Jan 2016 17:37:41 -0500 Received: from mail-wm0-x230.google.com ([2a00:1450:400c:c09::230]:38686) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aF8KK-0001RS-P0 for qemu-devel@nongnu.org; Fri, 01 Jan 2016 17:37:40 -0500 Received: by mail-wm0-x230.google.com with SMTP id b14so116790944wmb.1 for ; Fri, 01 Jan 2016 14:37:40 -0800 (PST) Sender: Paolo Bonzini References: From: Paolo Bonzini Message-ID: <5686FFAF.3070205@redhat.com> Date: Fri, 1 Jan 2016 23:37:35 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] Possible reference leak in device_set_realized(...) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ilya Lesokhin , "qemu-devel@nongnu.org" Cc: Haggai Eran , Knut Omang 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