qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>,
	virtio-fs-list <virtio-fs@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Virtio-fs] [PATCH] virtiofsd: Disable remote posix locks by default
Date: Thu, 6 Aug 2020 13:46:45 -0400	[thread overview]
Message-ID: <20200806174645.GG367847@redhat.com> (raw)
In-Reply-To: <20200806174129.GK2711@work-vm>

On Thu, Aug 06, 2020 at 06:41:29PM +0100, Dr. David Alan Gilbert wrote:
> * misono.tomohiro@fujitsu.com (misono.tomohiro@fujitsu.com) wrote:
> > > Right now we enable remote posix locks by default. That means when guest does a posix lock it sends request to server
> > > (virtiofsd). But currently we only support non-blocking posix lock and return -EOPNOTSUPP for blocking version.
> > > 
> > > This means that existing applications which are doing blocking posix locks get -EOPNOTSUPP and fail. To avoid this,
> > > people have been running virtiosd with option "-o no_posix_lock". For new users it is still a surprise and trial and error
> > > takes them to this option.
> > > 
> > > Given posix lock implementation is not complete in virtiofsd, disable it by default. This means that posix locks will work
> > > with-in applications in a guest but not across guests. Anyway we don't support sharing filesystem among different guests
> > > yet in virtiofs so this should not lead to any kind of surprise or regression and will make life little easier for virtiofs users.
> > > 
> > > Reported-by: Aa Aa <jimbothom@yandex.com>
> > > Suggested-by: Miklos Szeredi <mszeredi@redhat.com>
> > > Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
> > > ---
> > >  tools/virtiofsd/passthrough_ll.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > We should update docs/tools/virtiofsd.rst as well. Given that:
> >  Reviewed-by: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
> 
> Fixed up the doc.

Aha.. Looks like we were looking at this at the same time.

Thanks for taking care of this Dave.

Vivek



  reply	other threads:[~2020-08-06 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 16:18 [PATCH] virtiofsd: Disable remote posix locks by default Vivek Goyal
2020-08-03  9:57 ` [Virtio-fs] " Stefan Hajnoczi
2020-08-06  8:20 ` misono.tomohiro
2020-08-06 17:41   ` Dr. David Alan Gilbert
2020-08-06 17:46     ` Vivek Goyal [this message]
2020-08-06 17:46   ` Vivek Goyal
2020-08-06 17:45 ` Dr. David Alan Gilbert

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=20200806174645.GG367847@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=misono.tomohiro@fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtio-fs@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;
as well as URLs for NNTP newsgroup(s).