From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: Horst Birthelmer <horst@birthelmer.de>
Cc: miklos@szeredi.hu, joannelkoong@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ak: fuse: fix premature writetrhough request for large folio
Date: Wed, 14 Jan 2026 17:05:51 +0800 [thread overview]
Message-ID: <03d69c33-e7c9-4160-890f-3b7f65de37d5@linux.alibaba.com> (raw)
In-Reply-To: <aWdYxTEO29S91qp-@fedora.fritz.box>
On 1/14/26 4:58 PM, Horst Birthelmer wrote:
>
> Hi Jingbo,
>
> On Wed, Jan 14, 2026 at 01:56:15PM +0800, Jingbo Xu wrote:
>> When large folio is enabled and the initial folio offset exceeds
>> PAGE_SIZE, e.g. the position resides in the second page of a large
>> folio, after the folio copying the offset (in the page) won't be updated
>> to 0 even though the expected range is successfully copied until the end
>> of the folio. In this case fuse_fill_write_pages() exits prematurelly
>> before the request has reached the max_write/max_pages limit.
>>
>> Fix this by eliminating page offset entirely and use folio offset
>> instead.
>>
>> Fixes: d60a6015e1a2 ("fuse: support large folios for writethrough writes")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
>> ---
>> fs/fuse/file.c | 10 ++++------
>> 1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
>> index 625d236b881b..6aafb32338b6 100644
>> --- a/fs/fuse/file.c
>> +++ b/fs/fuse/file.c
>> @@ -1272,7 +1272,6 @@ static ssize_t fuse_fill_write_pages(struct fuse_io_args *ia,
>> {
>> struct fuse_args_pages *ap = &ia->ap;
>> struct fuse_conn *fc = get_fuse_conn(mapping->host);
>> - unsigned offset = pos & (PAGE_SIZE - 1);
>> size_t count = 0;
>> unsigned int num;
>> int err = 0;
>> @@ -1299,7 +1298,7 @@ static ssize_t fuse_fill_write_pages(struct fuse_io_args *ia,
>> if (mapping_writably_mapped(mapping))
>> flush_dcache_folio(folio);
>>
>> - folio_offset = ((index - folio->index) << PAGE_SHIFT) + offset;
>> + folio_offset = offset_in_folio(folio, pos);
>> bytes = min(folio_size(folio) - folio_offset, num);
>>
>> tmp = copy_folio_from_iter_atomic(folio, folio_offset, bytes, ii);
>> @@ -1329,9 +1328,6 @@ static ssize_t fuse_fill_write_pages(struct fuse_io_args *ia,
>> count += tmp;
>> pos += tmp;
>> num -= tmp;
>> - offset += tmp;
>> - if (offset == folio_size(folio))
>> - offset = 0;
>>
>> /* If we copied full folio, mark it uptodate */
>> if (tmp == folio_size(folio))
>> @@ -1343,7 +1339,9 @@ static ssize_t fuse_fill_write_pages(struct fuse_io_args *ia,
>> ia->write.folio_locked = true;
>> break;
>> }
>> - if (!fc->big_writes || offset != 0)
>> + if (!fc->big_writes)
>> + break;
>> + if (folio_offset + tmp != folio_size(folio))
>> break;
>> }
>>
>> --
>> 2.19.1.6.gb485710b
>>
>>
>
>
> I think this might have been an oversight when moving from pages to folios.
>
> Reviewed-by: Horst Birthelmer <hbirthelmer@ddn.com>
Right, it's not triggered until large folio is enabled.
Thanks for the review :)
next prev parent reply other threads:[~2026-01-14 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 5:56 Jingbo Xu
2026-01-14 8:58 ` Horst Birthelmer
2026-01-14 9:05 ` Jingbo Xu [this message]
2026-01-14 9:04 ` Jingbo Xu
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=03d69c33-e7c9-4160-890f-3b7f65de37d5@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=horst@birthelmer.de \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
all inboxes | Powered by JetHome®