All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: virtio-fs-list <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] F_SETLKW not supported
Date: Mon, 20 Jul 2020 08:38:13 -0400	[thread overview]
Message-ID: <20200720123813.GA502563@redhat.com> (raw)
In-Reply-To: <CAOssrKeUnGKADi_d3yNvrMJ2JCum_MAc0MWfnu0bU3prrjj1jQ@mail.gmail.com>

On Mon, Jul 20, 2020 at 11:33:32AM +0200, Miklos Szeredi wrote:
> On Mon, Jul 20, 2020 at 10:01 AM Aa Aa <jimbothom@yandex.com> wrote:
> >
> > Hi
> >
> > I am trying to run some java apps via virtfs and some of the file locking (java) doesn't work. Here an exception (java) is thrown something about file locking:
> >
> > Here is the strace output:
> >
> >  3541 [pid 12461] openat(AT_FDCWD, "/mnt/<redacted> O_WRONLY|O_CREAT|O_APPEND, 0666 <unfinished ...>
> >  3542 [pid 12461] <... openat resumed>)       = 180
> >  3543 [pid 12461] fstat(180, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> >  3544 [pid 12461] fcntl(180, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0} <unfinished ...>
> >  3545 [pid 12461] <... fcntl resumed>)        = -1 EOPNOTSUPP (Operation not supported)
> 
> I think that's due to an incomplete implementation of POSIX locks in virtiofsd.
> 
> Try "no_posix_lock" option: that should make locks work, but only
> locally (i.e. inside the guest).
> 
> Vivek, do we maybe want to turn off remote posix locks by default
> until the implementation is complete?

Hi Miklos,

Disabling it by default till we support blocking version of locks is
probably a good idea. That way it will work out of box without
having to specify no_posix_lock. Anyway, we don't support virtiofs
in shared mode yet. I will send a patch.

Thanks
Vivek


      reply	other threads:[~2020-07-20 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  7:54 [Virtio-fs] F_SETLKW not supported Aa Aa
2020-07-20  9:33 ` Miklos Szeredi
2020-07-20 12:38   ` Vivek Goyal [this message]

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=20200720123813.GA502563@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=mszeredi@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.