From: Laurent Vivier <lvivier@redhat.com>
To: pannengyuan@huawei.com, mst@redhat.com, amit@kernel.org,
marcandre.lureau@redhat.com, pbonzini@redhat.com
Cc: liyiting@huawei.com, kuhn.chenqun@huawei.com,
qemu-devel@nongnu.org, zhang.zhanghailiang@huawei.com
Subject: Re: [PATCH] virtio-serial-bus: fix memory leak while attach virtio-serial-bus
Date: Mon, 2 Dec 2019 14:58:52 +0100 [thread overview]
Message-ID: <dad28876-1850-32f3-fe47-9e4ec2c68f20@redhat.com> (raw)
In-Reply-To: <1575285343-21864-1-git-send-email-pannengyuan@huawei.com>
On 02/12/2019 12:15, pannengyuan@huawei.com wrote:
> From: PanNengyuan <pannengyuan@huawei.com>
>
> ivqs/ovqs/c_ivq/c_ovq is forgot to cleanup in
> virtio_serial_device_unrealize, the memory leak stack is as bellow:
>
> Direct leak of 1290240 byte(s) in 180 object(s) allocated from:
> #0 0x7fc9bfc27560 in calloc (/usr/lib64/libasan.so.3+0xc7560)
> #1 0x7fc9bed6f015 in g_malloc0 (/usr/lib64/libglib-2.0.so.0+0x50015)
> #2 0x5650e02b83e7 in virtio_add_queue /mnt/sdb/qemu-4.2.0-rc0/hw/virtio/virtio.c:2327
> #3 0x5650e02847b5 in virtio_serial_device_realize /mnt/sdb/qemu-4.2.0-rc0/hw/char/virtio-serial-bus.c:1089
> #4 0x5650e02b56a7 in virtio_device_realize /mnt/sdb/qemu-4.2.0-rc0/hw/virtio/virtio.c:3504
> #5 0x5650e03bf031 in device_set_realized /mnt/sdb/qemu-4.2.0-rc0/hw/core/qdev.c:876
> #6 0x5650e0531efd in property_set_bool /mnt/sdb/qemu-4.2.0-rc0/qom/object.c:2080
> #7 0x5650e053650e in object_property_set_qobject /mnt/sdb/qemu-4.2.0-rc0/qom/qom-qobject.c:26
> #8 0x5650e0533e14 in object_property_set_bool /mnt/sdb/qemu-4.2.0-rc0/qom/object.c:1338
> #9 0x5650e04c0e37 in virtio_pci_realize /mnt/sdb/qemu-4.2.0-rc0/hw/virtio/virtio-pci.c:1801
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: PanNengyuan <pannengyuan@huawei.com>
> ---
> hw/char/virtio-serial-bus.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c
> index 3325904..da9019a 100644
> --- a/hw/char/virtio-serial-bus.c
> +++ b/hw/char/virtio-serial-bus.c
> @@ -1126,9 +1126,15 @@ static void virtio_serial_device_unrealize(DeviceState *dev, Error **errp)
> {
> VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> VirtIOSerial *vser = VIRTIO_SERIAL(dev);
> + int i;
>
> QLIST_REMOVE(vser, next);
>
> + for (i = 0; i <= vser->bus.max_nr_ports; i++) {
> + virtio_del_queue(vdev, 2 * i);
> + virtio_del_queue(vdev, 2 * i + 1);
> + }
> +
According to virtio_serial_device_realize() and the number of
virtio_add_queue(), I think you have more queues to delete:
4 + 2 * vser->bus.max_nr_ports
(for vser->ivqs[0], vser->ovqs[0], vser->c_ivq, vser->c_ovq,
vser->ivqs[i], vser->ovqs[i]).
Thanks,
Laurent
next prev parent reply other threads:[~2019-12-02 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 11:15 [PATCH] virtio-serial-bus: fix memory leak while attach virtio-serial-bus pannengyuan
2019-12-02 13:58 ` Laurent Vivier [this message]
2019-12-03 0:53 ` pannengyuan
2019-12-03 5:37 ` Michael S. Tsirkin
2019-12-03 6:17 ` pannengyuan
2019-12-03 14:28 ` Amit Shah
2019-12-03 8:32 ` Laurent Vivier
2019-12-04 3:02 ` pannengyuan
2019-12-04 9:03 ` 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=dad28876-1850-32f3-fe47-9e4ec2c68f20@redhat.com \
--to=lvivier@redhat.com \
--cc=amit@kernel.org \
--cc=kuhn.chenqun@huawei.com \
--cc=liyiting@huawei.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pannengyuan@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).