qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	kuhn.chenqun@huawei.com, qemu-devel@nongnu.org
Cc: liyiting@huawei.com,
	"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	pannengyuan@huawei.com, zhang.zhanghailiang@huawei.com
Subject: Re: [PATCH] vl: fix memory leak in configure_accelerators
Date: Wed, 8 Jan 2020 15:59:46 +0100	[thread overview]
Message-ID: <d5626e7e-31fc-9065-7654-028c1af1d979@redhat.com> (raw)
In-Reply-To: <2bf0ae4f-b024-c421-b9d2-eefe99453e04@redhat.com>

On 08/01/20 15:56, Philippe Mathieu-Daudé wrote:
> On 1/8/20 12:42 PM, kuhn.chenqun@huawei.com wrote:
>> From: Chen Qun <kuhn.chenqun@huawei.com>
>>
>> The accel_list forgot to free, the asan output:
>>
>> Direct leak of 16 byte(s) in 1 object(s) allocated from:
>>      #0 0xffff919331cb in __interceptor_malloc
>> (/lib64/libasan.so.4+0xd31cb)
>>      #1 0xffff913f7163 in g_malloc (/lib64/libglib-2.0.so.0+0x57163)
>>      #2 0xffff91413d9b in g_strsplit (/lib64/libglib-2.0.so.0+0x73d9b)
>>      #3 0xaaab42fb58e7 in configure_accelerators /qemu/vl.c:2777
>>      #4 0xaaab42fb58e7 in main /qemu/vl.c:4121
>>      #5 0xffff8f9b0b9f in __libc_start_main (/lib64/libc.so.6+0x20b9f)
>>      #6 0xaaab42fc1dab 
>> (/qemu/build/aarch64-softmmu/qemu-system-aarch64+0x8b1dab)
>>
>> Indirect leak of 4 byte(s) in 1 object(s) allocated from:
>>      #0 0xffff919331cb in __interceptor_malloc
>> (/lib64/libasan.so.4+0xd31cb)
>>      #1 0xffff913f7163 in g_malloc (/lib64/libglib-2.0.so.0+0x57163)
>>      #2 0xffff9141243b in g_strdup (/lib64/libglib-2.0.so.0+0x7243b)
>>      #3 0xffff91413e6f in g_strsplit (/lib64/libglib-2.0.so.0+0x73e6f)
>>      #4 0xaaab42fb58e7 in configure_accelerators /qemu/vl.c:2777
>>      #5 0xaaab42fb58e7 in main /qemu/vl.c:4121
>>      #6 0xffff8f9b0b9f in __libc_start_main (/lib64/libc.so.6+0x20b9f)
>>      #7 0xaaab42fc1dab 
>> (/qemu/build/aarch64-softmmu/qemu-system-aarch64+0x8b1dab)
>>
>> Reported-by: Euler Robot <euler.robot@huawei.com>
>> Signed-off-by: Chen Qun <kuhn.chenqun@huawei.com>
> 
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> 
>> ---
>>   vl.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/vl.c b/vl.c
>> index 86474a55c9..035a24e52b 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -2788,6 +2788,7 @@ static void configure_accelerators(const char
>> *progname)
>>                   error_report("invalid accelerator %s", *tmp);
>>               }
>>           }
>> +        g_strfreev(accel_list);
>>       } else {
>>           if (accel != NULL) {
>>               error_report("The -accel and \"-machine accel=\" options
>> are incompatible");
>>
> 

Cc; qemu-trivial@nongnu.org



  reply	other threads:[~2020-01-08 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 11:42 [PATCH] vl: fix memory leak in configure_accelerators kuhn.chenqun
2020-01-08 14:56 ` Philippe Mathieu-Daudé
2020-01-08 14:59   ` Paolo Bonzini [this message]
2020-01-08 15:13 ` 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=d5626e7e-31fc-9065-7654-028c1af1d979@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kuhn.chenqun@huawei.com \
    --cc=liyiting@huawei.com \
    --cc=pannengyuan@huawei.com \
    --cc=philmd@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).