[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210119110654.11817-1-wu-yan@tcl.com>
Date: Tue, 19 Jan 2021 19:06:54 +0800
From: Rokudo Yan <wu-yan@....com>
To: <balsini@...roid.com>
CC: <akailash@...gle.com>, <amir73il@...il.com>, <axboe@...nel.dk>,
<bergwolf@...il.com>, <duostefano93@...il.com>,
<dvander@...gle.com>, <fuse-devel@...ts.sourceforge.net>,
<gscrivan@...hat.com>, <jannh@...gle.com>,
<kernel-team@...roid.com>, <linux-fsdevel@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <maco@...roid.com>,
<miklos@...redi.hu>, <palmer@...belt.com>,
<paullawrence@...gle.com>, <trapexit@...wn.link>, <wu-yan@....com>,
<zezeozue@...gle.com>
Subject: Re: [PATCH RESEND V11 0/7] fuse: Add support for passthrough read/write
on Mon, Jan 18, 2021 at 5:27 PM Alessio Balsini <balsini@...roid.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.
Powered by blists - more mailing lists