From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"Andreas Färber" <afaerber@suse.de>,
"Anthony Liguori" <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL for-2.0 1/7] vl.c: Fix memory leak in qemu_register_machine()
Date: Wed, 19 Mar 2014 22:45:36 +0100 [thread overview]
Message-ID: <1395265542-384-2-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1395265542-384-1-git-send-email-afaerber@suse.de>
From: Christian Borntraeger <borntraeger@de.ibm.com>
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>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
vl.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/vl.c b/vl.c
index f0fe48b..0e82f06 100644
--- a/vl.c
+++ b/vl.c
@@ -1587,14 +1587,16 @@ static void machine_class_init(ObjectClass *oc, void *data)
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;
}
--
1.8.4.5
next prev parent reply other threads:[~2014-03-19 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 21:45 [Qemu-devel] [PULL for-2.0-rc1 0/7] QOM devices patch queue 2014-03-19 Andreas Färber
2014-03-19 21:45 ` Andreas Färber [this message]
2014-03-19 21:45 ` [Qemu-devel] [PULL for-2.0 2/7] vl.c: Fix OpenBSD compilation issue due to namespace collisions Andreas Färber
2014-03-19 21:45 ` [Qemu-devel] [PULL for-2.0 3/7] qom: Split object_property_set_link() Andreas Färber
2014-03-19 21:45 ` [Qemu-devel] [PULL for-2.0 4/7] qom: Don't make link NULL on object_property_set_link() failure Andreas Färber
2014-03-19 21:45 ` [Qemu-devel] [PULL for-2.0 5/7] qom: Make QOM link property unref optional Andreas Färber
2014-03-19 21:45 ` [Qemu-devel] [PULL for-2.0 6/7] qom: Add check() argument to object_property_add_link() Andreas Färber
2014-03-19 21:45 ` [Qemu-devel] [PULL for-2.0 7/7] virtio-rng: Avoid default_backend refcount leak Andreas Färber
2014-03-19 22:38 ` [Qemu-devel] [PULL for-2.0-rc1 0/7] QOM devices patch queue 2014-03-19 Peter Maydell
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=1395265542-384-2-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=borntraeger@de.ibm.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).