linux-ext4 - [Bug 202809] ext4: ext4_xattr_ibody_get:591: comm systemd-journal: corrupted in-inode xattr

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-202809-13602-vgkRVf2C9V@https.bugzilla.kernel.org/>
Date:   Fri, 08 Mar 2019 18:10:52 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 202809] ext4: ext4_xattr_ibody_get:591: comm systemd-journal:
 corrupted in-inode xattr

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

--- Comment #2 from Theodore Tso (tytso@....edu) ---
Can you try reproducing the problem when using something more robust than an
emmc storage card?   The errors:

Multiply-claimed block(s) in inode 164223: 656535

alongside the xattr errors strongly suggest read or writes being corrupted.

So the first thing I would ask is: (a) can you reproduce this on multiple emmc
cards?   (b) can you use some other storage, say, a USB-attached SSD, as
opposed to crap flash (or to be politically correct, "cost-optimized flash" :-)

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