linux-ext4 - [Bug 201685] ext4 file system corruption

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: <bug-201685-13602-uROQRxta21@https.bugzilla.kernel.org/>
Date:   Mon, 03 Dec 2018 21:20:09 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 201685] ext4 file system corruption

https://bugzilla.kernel.org/show_bug.cgi?id=201685

--- Comment #211 from Michel Roelofs (michel@...helroelofs.nl) ---
When I ran updatedb on 4.19.6, RETPOLINE disabled, I triggered within 2 minutes
the following errors (which I never saw with 4.14.x and older):
[  117.180537] BTRFS error (device dm-8): bad tree block start, want 614367232
have 23591879
[  117.222142] BTRFS info (device dm-8): read error corrected: ino 0 off
614367232 (dev /dev/mapper/linux-lxc sector 1216320)

And ~20 minutes later (while again running updatedb and compiling the kernel):
[ 1328.804705] EXT4-fs error (device dm-1): ext4_iget:4851: inode #7606807:
comm updatedb: checksum invalid

With debugfs I located the file of that inode, then I did an ls on it:
root@...r:# ls -l /home//michel/src/linux/linux/drivers/firmware/efi/test/
ls: cannot access '/home//michel/src/linux/linux/drivers/firmware/efi/test/':
Bad message
(reproduces)

Dropping dentry and inode cache (echo 2 > /proc/sys/vm/drop_caches) didn't
resolve this, but dropping all caches (echo 3 > /proc/sys/vm/drop_caches) did.

Both a simple 'ls' and also 'debugfs -R 'ncheck <inode>' did show errors, which
were resolved by the 'echo 3 > /proc/sys/vm/drop_caches'. See my comment #168
for 4.19.5.

My next step is to try without SMP. Does anybody have suggestions what else I
can try, or where I should look? What information to share?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.