lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52674b2d-627f-428a-89f7-36c39caa76fe@linux.alibaba.com>
Date: Thu, 15 Jan 2026 10:11:01 +0800
From: Jingbo Xu <jefflexu@...ux.alibaba.com>
To: Joanne Koong <joannelkoong@...il.com>
Cc: miklos@...redi.hu, linux-fsdevel@...r.kernel.org,
 linux-kernel@...r.kernel.org, horst@...thelmer.de,
 joseph.qi@...ux.alibaba.com
Subject: Re: [PATCH v2] fuse: fix premature writetrhough request for large
 folio

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@...ux.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@...r.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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ