Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3381749ybl; Sun, 11 Aug 2019 22:37:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJMcZNXcqS18xR+DaByzi8RxryS/Fj9Z+mVXNKiZPkVmumbG/OiOumxNYML062XZ+OvIZL X-Received: by 2002:a65:690f:: with SMTP id s15mr27980782pgq.432.1565588261065; Sun, 11 Aug 2019 22:37:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565588261; cv=none; d=google.com; s=arc-20160816; b=cf+lOzpKexOG5XVqgRO6jSGZ9eAIMUrEKXgLNW47oTs/KJvmUedUrXgxK+t3xw5lZ3 RbyLK/I5TBGH279F7hBhxXrFnozEtML/0Q9+vc9NdAu0YsfOk1eNVDQVu734iZ+SdGmZ 4BHnpmLdaAuy8JfuGQkN+7T0qfjKzDn8S2KYNAHuYUPMK94RNgoy+QBlT2M6teImGB7N XUbR1QmXR/MftTdfb7GOJvJL8TLLhfXBfJDTRn8LC5yEaLOPxo+QFwEnYGoClt2gHy+1 R/ORjPm/TNA16STy31dUGJ5O3oyx3peXo+Y9liFUizir8nyzOMaqw9EgIk7NQ+ozJqVA NPiA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:thread-index:thread-topic :content-transfer-encoding:mime-version:subject:references :in-reply-to:message-id:cc:to:from:date; bh=YqyAo21kdMDEDmVAzI7gyt8LP3WR/tp18FEaUJQA7RE=; b=C/tBTJe/R8GkEfUBaEDJlyWBOhqZVlIc0VPfJ7+UpBkUwSclCbXYgB0oVG0lQhMi0L fZYwtLyl54RpMUDMJfW8ZbOiaSclXdkVEYzT8UafkuEY9EiREJWKHjWDQG0JrTLcZqLt KkdBRakj7idPcwV2sTcL1OlxObjoOswDdX/XBK2/HjfLJT8TJEx3zKsVati0hDuOdH8P /FAb/sjQYRJvxxVZCk6tCItzXjQ1RC4OBbPJyJqUGAQsZIlkwuJaSJcGSniYrlx+ml9h nEZzLGYEz2TGUhqWHEv7jWyOhps09MMQwfyLudshUKBBHTC7dsxMt8CIVmgjEYxRvo/H k2bw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 6si33220407pgb.201.2019.08.11.22.37.25; Sun, 11 Aug 2019 22:37:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726486AbfHLFgu (ORCPT + 99 others); Mon, 12 Aug 2019 01:36:50 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45502 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725822AbfHLFgt (ORCPT ); Mon, 12 Aug 2019 01:36:49 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 001608E582; Mon, 12 Aug 2019 05:36:48 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E43886092D; Mon, 12 Aug 2019 05:36:48 +0000 (UTC) Received: from zmail21.collab.prod.int.phx2.redhat.com (zmail21.collab.prod.int.phx2.redhat.com [10.5.83.24]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id CD3732551B; Mon, 12 Aug 2019 05:36:48 +0000 (UTC) Date: Mon, 12 Aug 2019 01:36:48 -0400 (EDT) From: Pankaj Gupta To: "Michael S. Tsirkin" Cc: amit@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org, virtualization@lists.linux-foundation.org, jasowang@redhat.com, linux-kernel@vger.kernel.org, xiaohli@redhat.com Message-ID: <361928616.7829318.1565588208467.JavaMail.zimbra@redhat.com> In-Reply-To: <20190810141019-mutt-send-email-mst@kernel.org> References: <20190809064847.28918-1-pagupta@redhat.com> <20190809064847.28918-2-pagupta@redhat.com> <20190810141019-mutt-send-email-mst@kernel.org> Subject: Re: [PATCH v3 1/2] virtio_console: free unused buffers with port delete MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.116.104, 10.4.195.23] Thread-Topic: virtio_console: free unused buffers with port delete Thread-Index: xwxGlAEv6xkpmfow2TwRUq1nvFYnwA== X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Mon, 12 Aug 2019 05:36:49 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > On Fri, Aug 09, 2019 at 12:18:46PM +0530, Pankaj Gupta wrote: > > The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset") > > deferred 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. > > So why not reuse the buffers that are already there in this case? > Seems quite possible. I took this approach because reusing the buffers will involve tweaking the existing core functionality like managing the the virt queue indexes. Compared to that deleting the buffers while hot-unplugging port is simple and was working fine before. It seems logically correct as well. I agree we need a spec change for this. > > > 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. > > > > Reported-by: Xiaohui Li > > Fixes: a7a69ec0d8e4 ("virtio_console: free buffers after reset") > > Cc: stable@vger.kernel.org > > Signed-off-by: Pankaj Gupta > > This is really a revert of a7a69ec0d8e4, just tagged confusingly. > > And the original is also supposed to be a bugfix. > So how will the original bug be fixed? Yes, Even I was confused while adding this tag. I will remove remove 'fixes' tag completely for this patch? because its a revert to original behavior which also is a bugfix. > > "this is the best we can do" is rarely the case. > > I am not necessarily against the revert. But if we go that way then what > we need to do is specify the behaviour in the spec, since strict spec > compliance is exactly what the original patch was addressing. Agree. > > In particular, we'd document that console has a special property that > when port is detached virtqueue is considered stopped, device must not > use any buffers, and it is legal to take buffers out of the device. Yes. This documents the exact scenario. Thanks. You want me to send a patch for the spec change? Best regards, Pankaj > > > > > --- > > 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 7270e7b69262..e8be82f1bae9 100644 > > --- a/drivers/char/virtio_console.c > > +++ b/drivers/char/virtio_console.c > > @@ -1494,15 +1494,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); > > } > > > > @@ -1938,11 +1948,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.21.0 >