From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Hao Xu <hao.xu@linux.dev>, fuse-devel@lists.sourceforge.net
Cc: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org,
Wanpeng Li <wanpengli@tencent.com>,
cgxu519@mykernel.net
Subject: Re: [RFC PATCH] fuse: invalidate page cache pages before direct write
Date: Mon, 26 Jun 2023 20:23:55 +0200 [thread overview]
Message-ID: <7da6719c-23ee-736e-6787-1aad56d22e07@fastmail.fm> (raw)
In-Reply-To: <0625d0cb-2a65-ffae-b072-e14a3f6c7571@linux.dev>
On 6/8/23 09:17, Hao Xu wrote:
> Ping...
>
> On 5/9/23 16:01, Hao Xu wrote:
>> From: Hao Xu <howeyxu@tencent.com>
>>
>> In FOPEN_DIRECT_IO, page cache may still be there for a file, direct
>> write should respect that and invalidate the corresponding pages so
>> that page cache readers don't get stale data. Another thing this patch
>> does is flush related pages to avoid its loss.
>>
>> Signed-off-by: Hao Xu <howeyxu@tencent.com>
>> ---
>>
>> Reference:
>> https://lore.kernel.org/linux-fsdevel/ee8380b3-683f-c526-5f10-1ce2ee6f79ad@linux.dev/#:~:text=I%20think%20this%20problem%20exists%20before%20this%20patchset
>>
>> fs/fuse/file.c | 14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
>> index 89d97f6188e0..edc84c1dfc5c 100644
>> --- a/fs/fuse/file.c
>> +++ b/fs/fuse/file.c
>> @@ -1490,7 +1490,8 @@ ssize_t fuse_direct_io(struct fuse_io_priv *io,
>> struct iov_iter *iter,
>> int write = flags & FUSE_DIO_WRITE;
>> int cuse = flags & FUSE_DIO_CUSE;
>> struct file *file = io->iocb->ki_filp;
>> - struct inode *inode = file->f_mapping->host;
>> + struct address_space *mapping = file->f_mapping;
>> + struct inode *inode = mapping->host;
>> struct fuse_file *ff = file->private_data;
>> struct fuse_conn *fc = ff->fm->fc;
>> size_t nmax = write ? fc->max_write : fc->max_read;
>> @@ -1516,6 +1517,17 @@ ssize_t fuse_direct_io(struct fuse_io_priv *io,
>> struct iov_iter *iter,
>> inode_unlock(inode);
>> }
>> + res = filemap_write_and_wait_range(mapping, pos, pos + count - 1);
>> + if (res)
>> + return res;
>> +
>> + if (write) {
>> + if (invalidate_inode_pages2_range(mapping,
>> + idx_from, idx_to)) {
>> + return -ENOTBLK;
>> + }
>> + }
>> +
>> io->should_dirty = !write && user_backed_iter(iter);
>> while (count) {
>> ssize_t nres;
>
Is this part not working?
if (!cuse && fuse_range_is_writeback(inode, idx_from, idx_to)) {
if (!write)
inode_lock(inode);
fuse_sync_writes(inode);
if (!write)
inode_unlock(inode);
}
Thanks,
Bernd
next prev parent reply other threads:[~2023-06-26 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 8:01 [RFC PATCH] fuse: invalidate page cache pages before direct write Hao Xu
2023-05-24 10:02 ` Hao Xu
2023-06-08 7:17 ` Hao Xu
2023-06-26 18:23 ` Bernd Schubert [this message]
2023-06-29 12:00 ` Hao Xu
2023-06-29 15:35 ` [fuse-devel] " Bernd Schubert
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=7da6719c-23ee-736e-6787-1aad56d22e07@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=cgxu519@mykernel.net \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hao.xu@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=wanpengli@tencent.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).