linux-kernel - Re: fscache corruption in Linux 5.17?

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: <1b39ecc0-cb2c-1655-aee7-f67a2253a8ea@leemhuis.info>
Date:   Mon, 20 Jun 2022 09:11:38 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     David Howells <dhowells@...hat.com>, Max Kellermann <mk@...all.com>
Cc:     linux-cachefs@...hat.com, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: fscache corruption in Linux 5.17?

On 31.05.22 11:13, David Howells wrote:
> Max Kellermann <mk@...all.com> wrote:
> 
>>> Can I put that down as a Tested-by?
>>
>> Yes.  A month later, still no new corruption.
> 
> Thanks!

David, is the patch from this thread ("fscache: Fix invalidation/lookup
race" --
https://lore.kernel.org/lkml/705278.1650462934@warthog.procyon.org.uk/ )
heading toward mainline any time soon? This is a tracked regression and
it looked to me like there hasn't been any progress in the last two weeks.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

#regzbot poke