Re: [PATCH] vl: fix memory leak in configure_accelerators

2020-01-08 Thread Laurent Vivier
Le 08/01/2020 à 12:42, kuhn.chen...@huawei.com a écrit : > From: Chen Qun > > The accel_list forgot to free, the asan output: > > Direct leak of 16 byte(s) in 1 object(s) allocated from: > #0 0x919331cb in __interceptor_malloc (/lib64/libasan.so.4+0xd31cb) > #1 0x913f7163 in g_ma

Re: [PATCH] vl: fix memory leak in configure_accelerators

2020-01-08 Thread Paolo Bonzini
On 08/01/20 15:56, Philippe Mathieu-Daudé wrote: > On 1/8/20 12:42 PM, kuhn.chen...@huawei.com wrote: >> From: Chen Qun >> >> The accel_list forgot to free, the asan output: >> >> Direct leak of 16 byte(s) in 1 object(s) allocated from: >> #0 0x919331cb in __interceptor_malloc >> (/lib64/

Re: [PATCH] vl: fix memory leak in configure_accelerators

2020-01-08 Thread Philippe Mathieu-Daudé
On 1/8/20 12:42 PM, kuhn.chen...@huawei.com wrote: From: Chen Qun The accel_list forgot to free, the asan output: Direct leak of 16 byte(s) in 1 object(s) allocated from: #0 0x919331cb in __interceptor_malloc (/lib64/libasan.so.4+0xd31cb) #1 0x913f7163 in g_malloc (/lib64/lib

[PATCH] vl: fix memory leak in configure_accelerators

2020-01-08 Thread kuhn.chenqun
From: Chen Qun The accel_list forgot to free, the asan output: Direct leak of 16 byte(s) in 1 object(s) allocated from: #0 0x919331cb in __interceptor_malloc (/lib64/libasan.so.4+0xd31cb) #1 0x913f7163 in g_malloc (/lib64/libglib-2.0.so.0+0x57163) #2 0x91413d9b in g_strsp