From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, stefanha@redhat.com, vgoyal@redhat.com,
slp@redhat.com, yezhenyu2@huawei.com, longpeng2@huawei.com,
berrange@redhat.com
Subject: [PULL 5/8] virtiofsd: Disable remote posix locks by default
Date: Fri, 28 Aug 2020 13:45:06 +0100 [thread overview]
Message-ID: <20200828124509.311210-6-dgilbert@redhat.com> (raw)
In-Reply-To: <20200828124509.311210-1-dgilbert@redhat.com>
From: Vivek Goyal <vgoyal@redhat.com>
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>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
---
docs/tools/virtiofsd.rst | 2 +-
tools/virtiofsd/passthrough_ll.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/tools/virtiofsd.rst b/docs/tools/virtiofsd.rst
index 824e713491..2cfdfd9ba2 100644
--- a/docs/tools/virtiofsd.rst
+++ b/docs/tools/virtiofsd.rst
@@ -67,7 +67,7 @@ Options
Disable racy fallback. The default is false.
* posix_lock|no_posix_lock -
- Enable/disable remote POSIX locks. The default is ``posix_lock``.
+ Enable/disable remote POSIX locks. The default is ``no_posix_lock``.
* readdirplus|no_readdirplus -
Enable/disable readdirplus. The default is ``readdirplus``.
diff --git a/tools/virtiofsd/passthrough_ll.c b/tools/virtiofsd/passthrough_ll.c
index 63d1d00565..a9feb90fd0 100644
--- a/tools/virtiofsd/passthrough_ll.c
+++ b/tools/virtiofsd/passthrough_ll.c
@@ -2823,7 +2823,7 @@ int main(int argc, char *argv[])
struct lo_data lo = {
.debug = 0,
.writeback = 0,
- .posix_lock = 1,
+ .posix_lock = 0,
.proc_self_fd = -1,
};
struct lo_map_elem *root_elem;
--
2.26.2
next prev parent reply other threads:[~2020-08-28 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 12:45 [PULL 0/8] migration and virtiofsd queue Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` [PULL 1/8] migration: unify the framework of socket-type channel Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` [PULL 2/8] migration: add vsock as data channel support Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` [PULL 3/8] migration: improve error reporting of block driver state name Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` [PULL 4/8] migration: tls: fix memory leak in migration_tls_get_creds Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` Dr. David Alan Gilbert (git) [this message]
2020-08-28 12:45 ` [PULL 6/8] virtiofsd: Remove "norace" from cmdline help and docs Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` [PULL 7/8] virtiofsd: drop CAP_DAC_READ_SEARCH Dr. David Alan Gilbert (git)
2020-08-28 12:45 ` [PULL 8/8] virtiofsd: probe unshare(CLONE_FS) and print an error Dr. David Alan Gilbert (git)
2020-08-28 21:29 ` [PULL 0/8] migration and virtiofsd queue Peter Maydell
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=20200828124509.311210-6-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=longpeng2@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=yezhenyu2@huawei.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).