Re: [PATCH v2 1/2] virtio-9p-device: fix memleak in virtio_9p_device_unrealize

2020-01-20 Thread Greg Kurz
On Fri, 17 Jan 2020 08:43:42 -0500 "Michael S. Tsirkin" wrote: > On Fri, Jan 17, 2020 at 01:52:53PM +0100, Christian Schoenebeck wrote: > > On Freitag, 17. Januar 2020 07:09:26 CET pannengy...@huawei.com wrote: > > > From: Pan Nengyuan > > > > > > v->vq forgot to cleanup in virtio_9p_device_unr

Re: [PATCH v2 1/2] virtio-9p-device: fix memleak in virtio_9p_device_unrealize

2020-01-17 Thread Michael S. Tsirkin
On Fri, Jan 17, 2020 at 01:52:53PM +0100, Christian Schoenebeck wrote: > On Freitag, 17. Januar 2020 07:09:26 CET pannengy...@huawei.com wrote: > > From: Pan Nengyuan > > > > v->vq forgot to cleanup in virtio_9p_device_unrealize, the memory leak > > stack is as follow: > > > > Direct leak of 143

Re: [PATCH v2 1/2] virtio-9p-device: fix memleak in virtio_9p_device_unrealize

2020-01-17 Thread Christian Schoenebeck
On Freitag, 17. Januar 2020 07:09:26 CET pannengy...@huawei.com wrote: > From: Pan Nengyuan > > v->vq forgot to cleanup in virtio_9p_device_unrealize, the memory leak > stack is as follow: > > Direct leak of 14336 byte(s) in 2 object(s) allocated from: > #0 0x7f819ae43970 (/lib64/libasan.so.5+

[PATCH v2 1/2] virtio-9p-device: fix memleak in virtio_9p_device_unrealize

2020-01-16 Thread pannengyuan
From: Pan Nengyuan v->vq forgot to cleanup in virtio_9p_device_unrealize, the memory leak stack is as follow: Direct leak of 14336 byte(s) in 2 object(s) allocated from: #0 0x7f819ae43970 (/lib64/libasan.so.5+0xef970) ??:? #1 0x7f819872f49d (/lib64/libglib-2.0.so.0+0x5249d) ??:? #2 0x55a