[PATCH v2] fuse: fix premature writetrhough request for large folio

Jingbo Xu posted 1 patch 3 weeks, 3 days ago
There is a newer version of this series
fs/fuse/file.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
[PATCH v2] fuse: fix premature writetrhough request for large folio
Posted by Jingbo Xu 3 weeks, 3 days ago
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
Reviewed-by: Horst Birthelmer <hbirthelmer@ddn.com>
Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
---
changes since v1:
- add Reviewed-by tag (Horst)

v1: https://yhbt.net/lore/all/20260114055615.17903-1-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
Re: [PATCH v2] fuse: fix premature writetrhough request for large folio
Posted by Joanne Koong 3 weeks, 3 days ago
On Wed, Jan 14, 2026 at 4:45 AM Jingbo Xu <jefflexu@linux.alibaba.com> 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

This should not need the stable tag or any backports. The bug cannot
trigger until the future patch for turning on large folios lands.

> Reviewed-by: Horst Birthelmer <hbirthelmer@ddn.com>
> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>

This LGTM, thanks for spotting this.

Reviewed-by: Joanne Koong <joannelkoong@gmail.com>

Btw, are your prod systems running fuse with large folios enabled? If
so, are your servers using writeback caching too?

Thanks,
Joanne

> ---
> changes since v1:
> - add Reviewed-by tag (Horst)
>
> v1: https://yhbt.net/lore/all/20260114055615.17903-1-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
>
Re: [PATCH v2] fuse: fix premature writetrhough request for large folio
Posted by Jingbo Xu 3 weeks, 2 days ago

On 1/15/26 2:41 AM, Joanne Koong wrote:
> On Wed, Jan 14, 2026 at 4:45 AM Jingbo Xu <jefflexu@linux.alibaba.com> 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
> 
> This should not need the stable tag or any backports. The bug cannot
> trigger until the future patch for turning on large folios lands.

I think 6.18 stable also needs this fix?

-- 
Thanks,
Jingbo

Re: [PATCH v2] fuse: fix premature writetrhough request for large folio
Posted by Jingbo Xu 3 weeks, 2 days ago
Hi Joanne,

On 1/15/26 9:56 AM, Jingbo Xu wrote:
> 
> 
> On 1/15/26 2:41 AM, Joanne Koong wrote:
>> On Wed, Jan 14, 2026 at 4:45 AM Jingbo Xu <jefflexu@linux.alibaba.com> 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
>>
>> This should not need the stable tag or any backports. The bug cannot
>> trigger until the future patch for turning on large folios lands.
> 
> I think 6.18 stable also needs this fix?
> 

Sorry I got it mixed up.  I remembered that the patch enabling large
folio is along with the whole patch series supporting large folio, but I
missed the fact that it was not merged to mainline.

So the stable tree indeed doesn't need the fix.  Sorry for the noise.  I
will drop the stable CC tag later.

-- 
Thanks,
Jingbo