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
| ||
|
Date: Fri, 23 Nov 2018 00:02:13 +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 #37 from Jimmy.Jazz@....net --- @Jen Axboe please read worth not worse in comment 33 I tried your patch for 4.19.3 and still get quite harmful ext4 errors like this one, EXT4-fs error (device dm-4): ext4_xattr_ibody_get:592: inode #4881425: comm rsync: corrupted in-inode xattr The filesystems were clean at boot time and the system was idle. tune2fs ends with FS Error count: 64 First error time: Fri Nov 23 00:19:25 2018 First error function: ext4_xattr_ibody_get First error line #: 592 First error inode #: 4881425 First error block #: 0 Last error time: Fri Nov 23 00:19:25 2018 Last error function: ext4_xattr_ibody_get Last error line #: 592 Last error inode #: 4881430 Last error block #: 0 MMP block number: 9255 MMP update interval: 5 If you are interested in its dumpe2fs result let me know. I don't use binary modules. -- You are receiving this mail because: You are watching the assignee of the bug.
Powered by blists - more mailing lists