Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp5973834ybe; Tue, 10 Sep 2019 11:34:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqzUU6h/8tY0EDwg/eULCpdKiUqhJtvhO9ZSorqIdB98nIYSj4lZkzeQcKmcnS9WfGhCoqhD X-Received: by 2002:a17:906:79d8:: with SMTP id m24mr26192506ejo.289.1568140453225; Tue, 10 Sep 2019 11:34:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568140453; cv=none; d=google.com; s=arc-20160816; b=zhXJJ+IFxCx1RGPfT5CLa3SCRK3/usEJ02UOSl/dGPQ819Nu591mCTWDkhk9bfV0UX ejfFBl7pN60OFWFTtVVIO1Qx3IDTeeUP/qvsDlGJzds6Lh6nQOyy74X+ru8W/41RYHyw ie49gdwJyLzHY/uH39eDamNzQsvc7kMUzsYV8ikbTI7Mh3Ej6zZundVZqySzD6UJ+q7M LkRgLj+HqpBXFNUx1mF0IrTXCoGBYim8d4Xl8KZY4j41Jc37Z1yvunLmjQnBoJ5iljWv T5+M72xzWA5yc4FR1hDUNv1VVGNNW172D8HRgT4LoLNxeIyBJp5Bx2X6dnMbm+kMmW0W uJmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=xd5J0j1O8RM23sIIIj9h2xCJg8OqHfg7OWxpv2iexsc=; b=HxQGh5JtfJjzqHC6zYF1fHaEXhO8WfP2su/iSK+JOGa3rxK+4acOovJ8bH8I+hP547 rGAsEhLtFwlrV2UXynkabTB3umaPDnZOZKQUlweo+4i6S0J9jo1TKNQWwzfV6npLO7SG +sZxLCBwzwAWsubf0QpBsfxgW0sFxvIgGpO0Ju9NwpipK3fXC7iaazkBW6JqR9g50XU0 0ziZf/qKZUqjKcM8GNxyWDVkQ/BsVEALpPRXNc/LwpNLNDEBUf2gzrfwXfw26/7n7fRz B7yMJ8LB7l0rqcpl8oRZHQf5Nx47hse8idR/j3/zTHXvHOWEMWWfk/Di1KNy8UcMO5uW M7Yw== 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 lu2si9843377ejb.253.2019.09.10.11.33.49; Tue, 10 Sep 2019 11:34:13 -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 S2389038AbfIIQSW (ORCPT + 99 others); Mon, 9 Sep 2019 12:18:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37872 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387912AbfIIQSV (ORCPT ); Mon, 9 Sep 2019 12:18:21 -0400 Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 82FB83B3C0 for ; Mon, 9 Sep 2019 16:18:21 +0000 (UTC) Received: by mail-qk1-f200.google.com with SMTP id y189so1526770qkb.14 for ; Mon, 09 Sep 2019 09:18:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=xd5J0j1O8RM23sIIIj9h2xCJg8OqHfg7OWxpv2iexsc=; b=pT6+oEDOenTuPDZ67JZcNml5/NR6xR3d5wsBBwyeRZTaaHEHpuWsYhh6HZ2vJUKPBF XpWfHwqezM7nIx/NXNWXPyqE3FP+vnSm0E9ZAqscYnwHX1EgPEpioWMtq9nR/e3QlM+x Esdr6ndZ2euHlkQFkT+FjSfzum1gqGco2pAvUH2V2IEAbhtsuqQ3alTEkiBycjm+4eE/ Uxgx3vjA7230WNxnuDVKns1okTlpzORcek+ibGo89izYVuQQk5r+n8MFLUw4L3EjaL1L hG4TFaLJ2T9yWqmDL+fDED2NS4a5lZx5evo2+A1DSCIqvQcPGWBOBmSfePFhwpxz2GGh hs1Q== X-Gm-Message-State: APjAAAURtWRrb9Tp1Efk1/Yq9KQlvcjuMAr9BSfzareC2T93gl9iwD2Z cWmCKS/gjjftgC7p6PitzfiqIbYnVP6HVIfRp6UygPzY9KA5QJoL09cdqfirLkwhxVm0ehtCffm x6FtCfWe3C+/6ORnWzhDHzUMq X-Received: by 2002:aed:316d:: with SMTP id 100mr442783qtg.20.1568045900871; Mon, 09 Sep 2019 09:18:20 -0700 (PDT) X-Received: by 2002:aed:316d:: with SMTP id 100mr442761qtg.20.1568045900648; Mon, 09 Sep 2019 09:18:20 -0700 (PDT) Received: from redhat.com ([80.74.107.118]) by smtp.gmail.com with ESMTPSA id c14sm8927771qta.80.2019.09.09.09.18.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Sep 2019 09:18:19 -0700 (PDT) Date: Mon, 9 Sep 2019 12:18:13 -0400 From: "Michael S. Tsirkin" To: Stefan Hajnoczi Cc: piaojun , Miklos Szeredi , linux-kernel@vger.kernel.org, virtio-fs@redhat.com, linux-fsdevel@vger.kernel.org, virtualization@lists.linux-foundation.org, Vivek Goyal Subject: Re: [Virtio-fs] [PATCH 00/18] virtiofs: Fix various races and cleanups round 1 Message-ID: <20190909121604-mutt-send-email-mst@kernel.org> References: <20190905194859.16219-1-vgoyal@redhat.com> <20190906103613.GH5900@stefanha-x1.localdomain> <866a1469-2c4b-59ce-cf3f-32f65e861b99@huawei.com> <20190909161455.GG20875@stefanha-x1.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190909161455.GG20875@stefanha-x1.localdomain> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 09, 2019 at 06:14:55PM +0200, Stefan Hajnoczi wrote: > On Sun, Sep 08, 2019 at 07:53:55PM +0800, piaojun wrote: > > > > > > On 2019/9/6 19:52, Miklos Szeredi wrote: > > > On Fri, Sep 6, 2019 at 12:36 PM Stefan Hajnoczi wrote: > > >> > > >> On Fri, Sep 06, 2019 at 10:15:14AM +0200, Miklos Szeredi wrote: > > >>> On Thu, Sep 5, 2019 at 9:49 PM Vivek Goyal wrote: > > >>>> > > >>>> Hi, > > >>>> > > >>>> Michael Tsirkin pointed out issues w.r.t various locking related TODO > > >>>> items and races w.r.t device removal. > > >>>> > > >>>> In this first round of cleanups, I have taken care of most pressing > > >>>> issues. > > >>>> > > >>>> These patches apply on top of following. > > >>>> > > >>>> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#virtiofs-v4 > > >>>> > > >>>> I have tested these patches with mount/umount and device removal using > > >>>> qemu monitor. For example. > > >>> > > >>> Is device removal mandatory? Can't this be made a non-removable > > >>> device? Is there a good reason why removing the virtio-fs device > > >>> makes sense? > > >> > > >> Hot plugging and unplugging virtio PCI adapters is common. I'd very > > >> much like removal to work from the beginning. > > > > > > Can you give an example use case? > > > > I think VirtFS migration need hot plugging, or it may cause QEMU crash > > or some problems. > > Live migration is currently unsupported. Hot unplugging the virtio-fs > device would allow the guest to live migrate successfully, so it's a > useful feature to work around the missing live migration support. > > Is this what you mean? > > Stefan Exactly. That's what I also said. To add to that, hotplug can not be negotiated, so it's not a feature we can easily add down the road if old guests crash on unplug. Thus a driver that does not support unplug should not claim to support removal. -- MST