linux-ext4 - Re: Aarch64 EXT4FS inode checksum failures - seems to be weak memory ordering issues

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 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]

Date:   Wed, 6 Jan 2021 23:00:45 +0100
From:   Arnd Bergmann <arnd@...nel.org>
To:     Will Deacon <will@...nel.org>
Cc:     Russell King - ARM Linux admin <linux@...linux.org.uk>,
        Mark Rutland <mark.rutland@....com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Theodore Ts'o" <tytso@....edu>,
        Andreas Dilger <adilger.kernel@...ger.ca>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: Aarch64 EXT4FS inode checksum failures - seems to be weak memory
 ordering issues

On Wed, Jan 6, 2021 at 10:04 PM Arnd Bergmann <arnd@...nel.org> wrote:
> On Wed, Jan 6, 2021 at 6:22 PM Will Deacon <will@...nel.org> wrote:
> > On Wed, Jan 06, 2021 at 01:52:53PM +0000, Russell King - ARM Linux admin wrote:
>
> I tried the Image-5.9.0 on a virtual machine with seven CPUs (two clusters)
> running in an M1 mac mini and ran these commands inside.
>
> > With that, I see the following after ten seconds or so:
> >
> >   EXT4-fs error (device sda2): ext4_lookup:1707: inode #674497: comm md5sum: iget: checksum invalid
> >
> > Russell, Mark -- does this recipe explode reliably for you too?
>
> Negative unfortunately -- no checksum mismatch so far, with 10 minutes
> elapsed. I'll keep it running a bit longer.

I managed to trigger the checksum mismatch once now, after around 40
minutes, with a second run going for 20 minutes without mismatch.

So it's not easily reproducible for me, but it does help to rule out
at least some of the hardware specific theories -- it's not just the
Cortex-A72, nor the CCI doing something weird, as neither of
them are in use here.

This is the output I got:

EXT4-fs error (device vda2): ext4_lookup:1707: inode #1185501: comm
md5sum: iget: checksum invalid
Aborting journal on device vda2-8.
EXT4-fs error (device vda2): ext4_journal_check_start:83: Detected
aborted journal
EXT4-fs (vda2): Remounting filesystem read-only
EXT4-fs (vda2): Remounting filesystem read-only
EXT4-fs error (device vda2): ext4_journal_check_start:83: Detected
aborted journal

      Arnd