From: Pan Nengyuan <pannengyuan@huawei.com>
To: Laurent Vivier <laurent@vivier.eu>, <pbonzini@redhat.com>
Cc: qemu-trivial@nongnu.org, zhang.zhanghailiang@huawei.com,
qemu-devel@nongnu.org, Euler Robot <euler.robot@huawei.com>
Subject: Re: [PATCH] vl: Don't mismatch g_strsplit()/g_free()
Date: Fri, 10 Jan 2020 16:06:59 +0800 [thread overview]
Message-ID: <97aff10c-d51f-3db2-3c59-183793dc6e3f@huawei.com> (raw)
In-Reply-To: <49907b09-2c11-1e95-9aa2-6b9cb0abf6cb@vivier.eu>
On 1/10/2020 3:59 PM, Laurent Vivier wrote:
> Le 10/01/2020 à 04:16, pannengyuan@huawei.com a écrit :
>> From: Pan Nengyuan <pannengyuan@huawei.com>
>>
>> It's a mismatch between g_strsplit and g_free, it will cause a memory leak as follow:
>>
>> [root@localhost]# ./aarch64-softmmu/qemu-system-aarch64 -accel help
>> Accelerators supported in QEMU binary:
>> tcg
>> kvm
>> =================================================================
>> ==1207900==ERROR: LeakSanitizer: detected memory leaks
>>
>> Direct leak of 8 byte(s) in 2 object(s) allocated from:
>> #0 0xfffd700231cb in __interceptor_malloc (/lib64/libasan.so.4+0xd31cb)
>> #1 0xfffd6ec57163 in g_malloc (/lib64/libglib-2.0.so.0+0x57163)
>> #2 0xfffd6ec724d7 in g_strndup (/lib64/libglib-2.0.so.0+0x724d7)
>> #3 0xfffd6ec73d3f in g_strsplit (/lib64/libglib-2.0.so.0+0x73d3f)
>> #4 0xaaab66be5077 in main /mnt/sdc/qemu-master/qemu-4.2.0-rc0/vl.c:3517
>> #5 0xfffd6e140b9f in __libc_start_main (/lib64/libc.so.6+0x20b9f)
>> #6 0xaaab66bf0f53 (./build/aarch64-softmmu/qemu-system-aarch64+0x8a0f53)
>>
>> Direct leak of 2 byte(s) in 2 object(s) allocated from:
>> #0 0xfffd700231cb in __interceptor_malloc (/lib64/libasan.so.4+0xd31cb)
>> #1 0xfffd6ec57163 in g_malloc (/lib64/libglib-2.0.so.0+0x57163)
>> #2 0xfffd6ec7243b in g_strdup (/lib64/libglib-2.0.so.0+0x7243b)
>> #3 0xfffd6ec73e6f in g_strsplit (/lib64/libglib-2.0.so.0+0x73e6f)
>> #4 0xaaab66be5077 in main /mnt/sdc/qemu-master/qemu-4.2.0-rc0/vl.c:3517
>> #5 0xfffd6e140b9f in __libc_start_main (/lib64/libc.so.6+0x20b9f)
>> #6 0xaaab66bf0f53 (./build/aarch64-softmmu/qemu-system-aarch64+0x8a0f53)
>>
>> Reported-by: Euler Robot <euler.robot@huawei.com>
>> Signed-off-by: Pan Nengyuan <pannengyuan@huawei.com>
>> ---
>> vl.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/vl.c b/vl.c
>> index 86474a55c9..2fa5cb3b9a 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -3476,7 +3476,7 @@ int main(int argc, char **argv, char **envp)
>> gchar **optname = g_strsplit(typename,
>> ACCEL_CLASS_SUFFIX, 0);
>> printf("%s\n", optname[0]);
>> - g_free(optname);
>> + g_strfreev(optname);
>> }
>> g_free(typename);
>> }
>>
>
> It is correct but could you try to cover all the cases?
>
> For instance, there is another one in qga/main.c:split_list().
Ok, I will try to do it.
Thanks.
>
> Thanks,
> Laurent
>
next prev parent reply other threads:[~2020-01-10 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 3:16 [PATCH] vl: Don't mismatch g_strsplit()/g_free() pannengyuan
2020-01-10 7:32 ` Marc-André Lureau
2020-01-10 7:59 ` Laurent Vivier
2020-01-10 8:06 ` Pan Nengyuan [this message]
2020-01-10 9:53 ` Laurent Vivier
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=97aff10c-d51f-3db2-3c59-183793dc6e3f@huawei.com \
--to=pannengyuan@huawei.com \
--cc=euler.robot@huawei.com \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
/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).