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

Message-ID: <YlsfSqysfKJqwDVz@rabbit.intern.cm-ag>
Date:   Sat, 16 Apr 2022 21:55:54 +0200
From:   Max Kellermann <mk@...all.com>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Max Kellermann <mk@...all.com>, dhowells@...hat.com,
        linux-cachefs@...hat.com, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Re: fscache corruption in Linux 5.17?

On 2022/04/16 13:38, Thorsten Leemhuis <regressions@...mhuis.info> wrote:
> Thx for the report. Maybe a bisection is what's needed here, but lets
> see what David says, maybe he has a idea already.

I wish I could do that, but it's very hard to reproduce; the first
reports came after a week or so.  That way, a bisect would take
months.  So yes, wait for David, because he might give a clue how to
trigger the problem more quickly to make a bisect practical.