linux-kernel - Re: [PATCH 5.15] fuse: Fix race condition in writethrough path A race

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3cfc568a-532f-44e0-a58e-6c3e042b173d@bsbernd.com>
Date: Tue, 14 Oct 2025 18:15:38 +0200
From: Bernd Schubert <bernd@...ernd.com>
To: Miklos Szeredi <miklos@...redi.hu>, Brian Foster <bfoster@...hat.com>
Cc: lu gu <giveme.gulu@...il.com>, Joanne Koong <joannelkoong@...il.com>,
 linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5.15] fuse: Fix race condition in writethrough path A race



On 10/14/25 18:10, Miklos Szeredi wrote:
> On Tue, 14 Oct 2025 at 15:57, Brian Foster <bfoster@...hat.com> wrote:
> 
>> But TBH, if the writeback thing or something similarly simple works for
>> resolving the immediate bug, I wouldnt worry too much about it
>> until/unless there are userspace fs' explicitly looking for that sort of
>> behavior. Just my .02.
> 
> Agreed.
> 
> I just feel it unfortunate that this is default in libfuse and so many
> filesystems will have auto_inval_data enabled which don't even need
> it, and some mixed read-write workloads suffering badly as a
> consequence.

Maybe we should disable it in libfuse-3.18 and hope for reports, in case
there are regressions?


Thanks,
Bernd