Re: [PATCH 2/3] stm32f2xx_timer: delay timer_new to avoid memleaks

2020-02-05 Thread Alistair Francis
On Tue, Feb 4, 2020 at 11:09 PM wrote: > > From: Pan Nengyuan > > There is a memory leak when we call 'device_list_properties' with typename = > stm32f2xx_timer. It's easy to reproduce as follow: > > virsh qemu-monitor-command vm1 --pretty '{"execute": > "device-list-properties", "arguments

Re: [PATCH 2/3] stm32f2xx_timer: delay timer_new to avoid memleaks

2020-02-05 Thread Philippe Mathieu-Daudé
On 2/5/20 8:06 AM, pannengy...@huawei.com wrote: From: Pan Nengyuan There is a memory leak when we call 'device_list_properties' with typename = stm32f2xx_timer. It's easy to reproduce as follow: virsh qemu-monitor-command vm1 --pretty '{"execute": "device-list-properties", "arguments":

[PATCH 2/3] stm32f2xx_timer: delay timer_new to avoid memleaks

2020-02-04 Thread pannengyuan
From: Pan Nengyuan There is a memory leak when we call 'device_list_properties' with typename = stm32f2xx_timer. It's easy to reproduce as follow: virsh qemu-monitor-command vm1 --pretty '{"execute": "device-list-properties", "arguments": {"typename": "stm32f2xx_timer"}}' This patch delay