From: Greg KH <gregkh@linuxfoundation.org>
To: amit@kernel.org, zhenwei pi <pizhenwei@bytedance.com>
Cc: amit@kernel.org, arnd@arndb.de,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virtio_console: remove vq buf while unpluging port
Date: Fri, 24 May 2019 20:51:32 +0200 [thread overview]
Message-ID: <20190524185132.GA10695@kroah.com> (raw)
In-Reply-To: <1556416204-30311-1-git-send-email-pizhenwei@bytedance.com>
On Sun, Apr 28, 2019 at 09:50:04AM +0800, zhenwei pi wrote:
> A bug can be easily reproduced:
> Host# cat guest-agent.xml
> <channel type="unix">
> <source mode="bind" path="/var/lib/libvirt/qemu/stretch.agent"/>
> <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/>
> </channel>
> Host# virsh attach-device instance guest-agent.xml
> Host# virsh detach-device instance guest-agent.xml
> Host# virsh attach-device instance guest-agent.xml
>
> and guest report: virtio-ports vport0p1: Error allocating inbufs
>
> The reason is that the port is unplugged and the vq buf still remained.
> So, fix two cases in this patch:
> 1, fix memory leak with attach-device/detach-device.
> 2, fix logic bug with attach-device/detach-device/attach-device.
>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> drivers/char/virtio_console.c | 21 +++++++++++++++------
> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
> index fbeb719..f6e37f4 100644
> --- a/drivers/char/virtio_console.c
> +++ b/drivers/char/virtio_console.c
> @@ -251,6 +251,7 @@ struct port {
>
> /* This is the very early arch-specified put chars function. */
> static int (*early_put_chars)(u32, const char *, int);
> +static void remove_vq(struct virtqueue *vq);
>
> static struct port *find_port_by_vtermno(u32 vtermno)
> {
> @@ -1550,6 +1551,9 @@ static void unplug_port(struct port *port)
> }
>
> remove_port_data(port);
> + spin_lock_irq(&port->inbuf_lock);
> + remove_vq(port->in_vq);
> + spin_unlock_irq(&port->inbuf_lock);
>
> /*
> * We should just assume the device itself has gone off --
> @@ -1945,17 +1949,22 @@ static const struct file_operations portdev_fops = {
> .owner = THIS_MODULE,
> };
>
> +static void remove_vq(struct virtqueue *vq)
> +{
> + struct port_buffer *buf;
> +
> + flush_bufs(vq, true);
> + while ((buf = virtqueue_detach_unused_buf(vq)))
> + free_buf(buf, true);
> +}
> +
> static void remove_vqs(struct ports_device *portdev)
> {
> struct virtqueue *vq;
>
> - virtio_device_for_each_vq(portdev->vdev, vq) {
> - struct port_buffer *buf;
> + virtio_device_for_each_vq(portdev->vdev, vq)
> + remove_vq(vq);
>
> - flush_bufs(vq, true);
> - while ((buf = virtqueue_detach_unused_buf(vq)))
> - free_buf(buf, true);
> - }
> portdev->vdev->config->del_vqs(portdev->vdev);
> kfree(portdev->in_vqs);
> kfree(portdev->out_vqs);
> --
> 2.7.4
Amit, any ideas if this is valid or not and if this should be applied?
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-24 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 1:50 [PATCH] virtio_console: remove vq buf while unpluging port zhenwei pi
2019-05-24 18:51 ` Greg KH [this message]
2019-05-28 12:59 ` Amit Shah
-- strict thread matches above, loose matches on Subject: below --
2019-05-05 1:53 zhenwei pi
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=20190524185132.GA10695@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pizhenwei@bytedance.com \
--cc=virtualization@lists.linux-foundation.org \
/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