From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: kvm@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, virtio-fs@redhat.com,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [for-6.1 v2 0/2] virtiofsd: Add support for FUSE_SYNCFS request
Date: Tue, 27 Apr 2021 12:28:13 +0100 [thread overview]
Message-ID: <YIf1TY4MbAQnCYG0@work-vm> (raw)
In-Reply-To: <20210426152135.842037-1-groug@kaod.org>
* Greg Kurz (groug@kaod.org) wrote:
> FUSE_SYNCFS allows the client to flush the host page cache.
> This isn't available in upstream linux yet, but the following
> tree can be used to test:
That looks OK to me; but we'll need to wait until syncfs lands in the
upstream kernel; we've got bitten before by stuff changing before it
actaully lands in the kernel.
Dave
> https://gitlab.com/gkurz/linux/-/tree/virtio-fs-sync
>
> 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):
> Update linux headers to 5.12-rc8 + FUSE_SYNCFS
> virtiofsd: Add support for FUSE_SYNCFS request
>
> include/standard-headers/drm/drm_fourcc.h | 23 ++++-
> include/standard-headers/linux/ethtool.h | 54 ++++++-----
> include/standard-headers/linux/fuse.h | 13 ++-
> include/standard-headers/linux/input.h | 2 +-
> .../standard-headers/rdma/vmw_pvrdma-abi.h | 7 ++
> linux-headers/asm-generic/unistd.h | 4 +-
> linux-headers/asm-mips/unistd_n32.h | 1 +
> linux-headers/asm-mips/unistd_n64.h | 1 +
> linux-headers/asm-mips/unistd_o32.h | 1 +
> linux-headers/asm-powerpc/kvm.h | 2 +
> linux-headers/asm-powerpc/unistd_32.h | 1 +
> linux-headers/asm-powerpc/unistd_64.h | 1 +
> linux-headers/asm-s390/unistd_32.h | 1 +
> linux-headers/asm-s390/unistd_64.h | 1 +
> linux-headers/asm-x86/kvm.h | 1 +
> linux-headers/asm-x86/unistd_32.h | 1 +
> linux-headers/asm-x86/unistd_64.h | 1 +
> linux-headers/asm-x86/unistd_x32.h | 1 +
> linux-headers/linux/kvm.h | 89 +++++++++++++++++++
> linux-headers/linux/vfio.h | 27 ++++++
> tools/virtiofsd/fuse_lowlevel.c | 19 ++++
> tools/virtiofsd/fuse_lowlevel.h | 13 +++
> tools/virtiofsd/passthrough_ll.c | 29 ++++++
> tools/virtiofsd/passthrough_seccomp.c | 1 +
> 24 files changed, 267 insertions(+), 27 deletions(-)
>
> --
> 2.26.3
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-04-27 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 15:21 [for-6.1 v2 0/2] virtiofsd: Add support for FUSE_SYNCFS request Greg Kurz
2021-04-26 15:21 ` [for-6.1 v2 1/2] Update linux headers to 5.12-rc8 + FUSE_SYNCFS Greg Kurz
2021-04-26 15:21 ` [for-6.1 v2 2/2] virtiofsd: Add support for FUSE_SYNCFS request Greg Kurz
2021-05-05 18:52 ` Vivek Goyal
2021-05-06 6:14 ` Greg Kurz
2021-04-27 11:28 ` Dr. David Alan Gilbert [this message]
2021-04-27 12:50 ` [for-6.1 v2 0/2] " 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=YIf1TY4MbAQnCYG0@work-vm \
--to=dgilbert@redhat.com \
--cc=cohuck@redhat.com \
--cc=groug@kaod.org \
--cc=kvm@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).