From: Rokudo Yan <wu-yan@tcl.com>
To: <balsini@android.com>
Cc: <akailash@google.com>, <amir73il@gmail.com>, <axboe@kernel.dk>,
<bergwolf@gmail.com>, <duostefano93@gmail.com>,
<dvander@google.com>, <fuse-devel@lists.sourceforge.net>,
<gscrivan@redhat.com>, <jannh@google.com>,
<kernel-team@android.com>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <maco@android.com>,
<miklos@szeredi.hu>, <palmer@dabbelt.com>,
<paullawrence@google.com>, <trapexit@spawn.link>,
<wu-yan@tcl.com>, <zezeozue@google.com>
Subject: Re: [PATCH RESEND V11 0/7] fuse: Add support for passthrough read/write
Date: Tue, 19 Jan 2021 19:06:54 +0800 [thread overview]
Message-ID: <20210119110654.11817-1-wu-yan@tcl.com> (raw)
In-Reply-To: <20210118192748.584213-1-balsini@android.com>
on Mon, Jan 18, 2021 at 5:27 PM Alessio Balsini <balsini@android.com> wrote:
>
> This is the 11th version of the series, rebased on top of v5.11-rc4.
> Please find the changelog at the bottom of this cover letter.
>
> Add support for file system passthrough read/write of files when enabled
> in userspace through the option FUSE_PASSTHROUGH.
[...]
Hi Allesio,
Could you please add support for passthrough mmap too ?
If the fuse file opened with passthrough actived, and then map (shared) to (another) process
address space using mmap interface. As access the file with mmap will pass the vfs cache of fuse,
but access the file with read/write will bypass the vfs cache of fuse, this may cause inconsistency.
eg. the reader read the fuse file with mmap() and the writer modify the file with write(), the reader
may not see the modification immediately since the writer bypass the vfs cache of fuse.
Actually we have already meet an issue caused by the inconsistency after applying fuse passthrough
scheme to our product.
Thanks,
yanwu.
next prev parent reply other threads:[~2021-01-19 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 19:27 [PATCH RESEND V11 0/7] fuse: Add support for passthrough read/write Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 1/7] fs: Generic function to convert iocb to rw flags Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 2/7] fuse: 32-bit user space ioctl compat for fuse device Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 3/7] fuse: Definitions and ioctl for passthrough Alessio Balsini
2021-01-19 6:33 ` Amir Goldstein
2021-01-19 11:51 ` Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 4/7] fuse: Passthrough initialization and release Alessio Balsini
2021-01-19 12:06 ` Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 5/7] fuse: Introduce synchronous read and write for passthrough Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 6/7] fuse: Handle asynchronous read and write in passthrough Alessio Balsini
2021-01-18 19:27 ` [PATCH RESEND V11 7/7] fuse: Use daemon creds in passthrough mode Alessio Balsini
2021-01-19 11:06 ` Rokudo Yan [this message]
2021-01-19 12:34 ` [PATCH RESEND V11 0/7] fuse: Add support for passthrough read/write Alessio Balsini
2021-01-22 11:06 ` Alessio Balsini
2021-01-25 2:39 ` wu-yan
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=20210119110654.11817-1-wu-yan@tcl.com \
--to=wu-yan@tcl.com \
--cc=akailash@google.com \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=balsini@android.com \
--cc=bergwolf@gmail.com \
--cc=duostefano93@gmail.com \
--cc=dvander@google.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=gscrivan@redhat.com \
--cc=jannh@google.com \
--cc=kernel-team@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=miklos@szeredi.hu \
--cc=palmer@dabbelt.com \
--cc=paullawrence@google.com \
--cc=trapexit@spawn.link \
--cc=zezeozue@google.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.