From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Marcel Apfelbaum" <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] small memory leak due to MachineClass rework
Date: Tue, 18 Mar 2014 16:57:48 +0200 [thread overview]
Message-ID: <20140318145748.GA28344@redhat.com> (raw)
In-Reply-To: <5327618D.5070007@de.ibm.com>
On Mon, Mar 17, 2014 at 09:56:45PM +0100, Christian Borntraeger wrote:
> Marcel,
>
> after
>
> 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.
> This fixes the small leak, but I have to cast away the constness of .name.
> Any better ideas?
>
>
> diff --git a/vl.c b/vl.c
> index 03488b9..b06d186 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1594,13+1594,14 @@ static void machine_class_init(ObjectClass *oc, void *data)
> int qemu_register_machine(QEMUMachine *m)
> {
> TypeInfo ti = {
> .name = g_strconcat(m->name, TYPE_MACHINE_SUFFIX, NULL),
> .parent = TYPE_MACHINE,
> .class_init = machine_class_init,
> .class_data = (void *)m,
> };
>
> type_register(&ti);
> + g_free((gpointer) ti.name);
>
> return 0;
> }
How about:
int qemu_register_machine(QEMUMachine *m)
{
+ char *name = g_strconcat(m->name, TYPE_MACHINE_SUFFIX, NULL);
TypeInfo ti = {
- .name = g_strconcat(m->name, TYPE_MACHINE_SUFFIX, NULL),
+ .name = name,
.parent = TYPE_MACHINE,
.class_init = machine_class_init,
.class_data = (void *)m,
};
type_register(&ti);
+ g_free(name);
return 0;
}
prev parent reply other threads:[~2014-03-18 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 20:56 [Qemu-devel] small memory leak due to MachineClass rework Christian Borntraeger
2014-03-17 21:25 ` Peter Maydell
2014-03-17 21:29 ` Christian Borntraeger
2014-03-17 21:38 ` Andreas Färber
2014-03-17 21:43 ` Marcel Apfelbaum
2014-03-18 14:57 ` Michael S. Tsirkin [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=20140318145748.GA28344@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=marcel.a@redhat.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).