From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Sebastian Hasler <sebastian.hasler@stuvus.uni-stuttgart.de>,
Greg Kurz <groug@kaod.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
virtio-fs@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: [PATCH v4 0/2] virtiofsd: Add support for FUSE_SYNCFS request
Date: Tue, 25 Jan 2022 15:12:10 +0100 [thread overview]
Message-ID: <20220125141213.361930-1-groug@kaod.org> (raw)
FUSE_SYNCFS allows the client to flush the host page cache.
v4: - based on upstream linux FUSE_SYNCFS
- added support for the '-o announce_submounts' case, i.e. client sends
a FUSE_SYNCFS request for each submount (identified by its root inode)
- adapted the case without '-o announce_submounts' so that syncfs() is
no longer called with lo->mutex held
v3: - track submounts and do per-submount syncfs() (Vivek)
- based on new version of FUSE_SYNCFS (still not upstream)
https://listman.redhat.com/archives/virtio-fs/2021-May/msg00025.html
v2: - based on new version of FUSE_SYNCFS
https://listman.redhat.com/archives/virtio-fs/2021-April/msg00166.html
- propagate syncfs() errors to client (Vivek)
Greg Kurz (2):
virtiofsd: Track mounts
virtiofsd: Add support for FUSE_SYNCFS request
tools/virtiofsd/fuse_lowlevel.c | 11 ++
tools/virtiofsd/fuse_lowlevel.h | 13 +++
tools/virtiofsd/passthrough_ll.c | 141 +++++++++++++++++++++++++-
tools/virtiofsd/passthrough_seccomp.c | 1 +
4 files changed, 163 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-25 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 14:12 Greg Kurz [this message]
2022-01-25 14:12 ` [PATCH v4 1/2] virtiofsd: Track mounts Greg Kurz
2022-01-26 22:47 ` Vivek Goyal
2022-01-26 23:02 ` [Virtio-fs] " Vivek Goyal
2022-01-27 11:42 ` Greg Kurz
2022-01-27 11:11 ` Greg Kurz
2022-01-25 14:12 ` [PATCH v4 2/2] virtiofsd: Add support for FUSE_SYNCFS request Greg Kurz
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=20220125141213.361930-1-groug@kaod.org \
--to=groug@kaod.org \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sebastian.hasler@stuvus.uni-stuttgart.de \
--cc=stefanha@redhat.com \
--cc=vgoyal@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 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).