mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pankaj Gupta <pagupta@redhat.com>
To: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Cc: amit@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
	mst@redhat.com, pagupta@redhat.com, xiaohli@redhat.com
Subject: [PATCH] virtio_console: free unused buffers with virtio port
Date: Mon,  4 Mar 2019 18:35:11 +0530	[thread overview]
Message-ID: <20190304130511.14450-1-pagupta@redhat.com> (raw)

  The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset")
  deffered detaching of unused buffer to virtio device unplug time. 

  This causes unplug/replug of single port in virtio device with an 
  error "Error allocating inbufs\n". As we don't free the unused buffers 
  attached with the port. Re-plug the same port tries to allocate new
  buffers in virtqueue and results in this error if queue is full. 

  This patch removes the unused buffers in vq's when we unplug the port.
  This is the best we can do as we cannot call device_reset because virtio 
  device is still active. This was the working behaviour before the change 
  introduced in commit b3258ff1d6.

  Reported-by: Xiaohui Li <xiaohli@redhat.com>
  Fixes: b3258ff1d6 ("virtio_console: free buffers after reset")
  Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
---
 drivers/char/virtio_console.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index fbeb71953526..5fbf2ac73111 100644
--- a/drivers/char/virtio_console.c
+++ b/drivers/char/virtio_console.c
@@ -1506,15 +1506,25 @@ static void remove_port(struct kref *kref)
 	kfree(port);
 }
 
+static void remove_unused_bufs(struct virtqueue *vq)
+{
+	struct port_buffer *buf;
+
+	while ((buf = virtqueue_detach_unused_buf(vq)))
+		free_buf(buf, true);
+}
+
 static void remove_port_data(struct port *port)
 {
 	spin_lock_irq(&port->inbuf_lock);
 	/* Remove unused data this port might have received. */
 	discard_port_data(port);
+	remove_unused_bufs(port->in_vq);
 	spin_unlock_irq(&port->inbuf_lock);
 
 	spin_lock_irq(&port->outvq_lock);
 	reclaim_consumed_buffers(port);
+	remove_unused_bufs(port->out_vq);
 	spin_unlock_irq(&port->outvq_lock);
 }
 
@@ -1950,11 +1960,9 @@ static void remove_vqs(struct ports_device *portdev)
 	struct virtqueue *vq;
 
 	virtio_device_for_each_vq(portdev->vdev, vq) {
-		struct port_buffer *buf;
 
 		flush_bufs(vq, true);
-		while ((buf = virtqueue_detach_unused_buf(vq)))
-			free_buf(buf, true);
+		remove_unused_bufs(vq);
 	}
 	portdev->vdev->config->del_vqs(portdev->vdev);
 	kfree(portdev->in_vqs);
-- 
2.20.1


             reply	other threads:[~2019-03-04 13:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 13:05 Pankaj Gupta [this message]
2019-03-04 13:28 ` Pankaj Gupta
2019-03-04 19:25 ` Michael S. Tsirkin
2019-03-05  7:09   ` Pankaj Gupta
2019-03-11  6:35     ` Michael S. Tsirkin
2019-03-11  6:53       ` Pankaj Gupta
2019-03-11  5:58 ` Pankaj Gupta
2019-03-11  6:36   ` Michael S. Tsirkin

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=20190304130511.14450-1-pagupta@redhat.com \
    --to=pagupta@redhat.com \
    --cc=amit@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xiaohli@redhat.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

all inboxes | Powered by JetHome®