[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190906103613.GH5900@stefanha-x1.localdomain>
Date: Fri, 6 Sep 2019 11:36:13 +0100
From: Stefan Hajnoczi <stefanha@...hat.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Vivek Goyal <vgoyal@...hat.com>, linux-fsdevel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, virtio-fs@...hat.com,
"Dr. David Alan Gilbert" <dgilbert@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>
Subject: Re: [PATCH 00/18] virtiofs: Fix various races and cleanups round 1
On Fri, Sep 06, 2019 at 10:15:14AM +0200, Miklos Szeredi wrote:
> On Thu, Sep 5, 2019 at 9:49 PM Vivek Goyal <vgoyal@...hat.com> 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.
Stefan
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists