From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Marcel Apfelbaum <marcel.a@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCHv2] vl.c: Fix memory leak in qemu_register_machine
Date: Wed, 19 Mar 2014 21:01:16 +0100 [thread overview]
Message-ID: <5329F78C.9020601@suse.de> (raw)
In-Reply-To: <20140319132148.GA27827@redhat.com>
Am 19.03.2014 14:21, schrieb Michael S. Tsirkin:
> On Wed, Mar 19, 2014 at 12:24:27PM +0100, Christian Borntraeger wrote:
>> since commit 261747f176f6 (vl: Use MachineClass instead of global
>> QEMUMachine list) valgrind complains about the following:
>>
>> ==54082== 57 bytes in 3 blocks are definitely lost in loss record 365 of
>> 729
>> ==54082== at 0x4031AFE: malloc (vg_replace_malloc.c:292)
>> ==54082== by 0x4145569: g_malloc (in
>> /usr/lib64/libglib-2.0.so.0.3400.2)
>> ==54082== by 0x415F9E9: g_strconcat (in
>> /usr/lib64/libglib-2.0.so.0.3400.2)
>> ==54082== by 0x80157FE7: qemu_register_machine (vl.c:1597)
>> ==54082== by 0x80208E6B: module_call_init (module.c:105)
>> ==54082== by 0x80013B91: main (vl.c:3000)
>>
>> Turns out that valgrind is right. We simply forget the memory that
>> g_strconcat has allocated. Lets free it after the type_register.
>> We need a 2nd variable due to constness of the name part of the
>> type structure.
>>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>
> Andreas can you pick this up pls?
I already had - updated with your Rb now.
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2014-03-19 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 11:24 [Qemu-devel] [PATCHv2] vl.c: Fix memory leak in qemu_register_machine Christian Borntraeger
2014-03-19 12:10 ` Andreas Färber
2014-03-19 13:21 ` Michael S. Tsirkin
2014-03-19 20:01 ` Andreas Färber [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=5329F78C.9020601@suse.de \
--to=afaerber@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=marcel.a@redhat.com \
--cc=mst@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.