| 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
| ||
|
Message-Id: <201104011407.p31E7vbQ026250@demeter2.kernel.org> Date: Fri, 1 Apr 2011 14:07:57 GMT From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 32182] EXT4-fs error: bad header/extent https://bugzilla.kernel.org/show_bug.cgi?id=32182 --- Comment #1 from Anonymous Emailer <anonymous@...nel-bugs.osdl.org> 2011-04-01 14:07:56 --- Reply-To: xiaoqiangnk@...il.com Could the bug be reproduced? If so, how to? On Wed, Mar 30, 2011 at 12:47 AM, <bugzilla-daemon@...zilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=32182 > > Summary: EXT4-fs error: bad header/extent > Product: File System > Version: 2.5 > Kernel Version: 2.6.38.1 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: high > Priority: P1 > Component: ext4 > AssignedTo: fs_ext4@...nel-bugs.osdl.org > ReportedBy: ramses.rommel@...il.com > Regression: No > > > I started noticing ext4-fs errors in my dmesg output, they look like this: > > EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760218: comm > dropbox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth > 0(0) > EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760208: comm > dropbox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth > 0(0) > EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760218: comm > thunderbird-bin: bad header/extent: invalid magic - magic 0, entries 0, max > 0(0), depth 0(0) > EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760208: comm > thunderbird-bin: bad header/extent: invalid magic - magic 0, entries 0, max > 0(0), depth 0(0) > > I fsck'ed the partition which showed nothing but the regular output but said > the file system was modified, after a reboot the same errors returned though. > I'm using e2fsprogs 1.41.14 and linux 2.6.38.1 and after a downgrade to linux > 2.6.37.5 the errors kept reappearing (I'll test 2.6.38.2 soon but I didn't find > commit messages that seemed relevant). > > I ran debugfs on one of the inodes: > > % debugfs -R 'stat <3760208>' /dev/disk/by-label/home > debugfs 1.41.14 (22-Dec-2010) > Inode: 3760208 Type: regular Mode: 0644 Flags: 0x80000 > Generation: 231468018 Version: 0x00000001 > User: 1000 Group: 100 Size: 42 > File ACL: 0 Directory ACL: 0 > Links: 1 Blockcount: 0 > Fragment: Address: 0 Number: 0 Size: 0 > ctime: 0x4b2a09ff -- Thu Dec 17 11:37:51 2009 > atime: 0x4d909367 -- Mon Mar 28 15:55:51 2011 > mtime: 0x490976f8 -- Thu Oct 30 09:57:28 2008 > EXTENTS: > > I'm not sure what extra info to give you, but I'd be glad to provide stuff you > need to reproduce/fix this. > > -- > Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching the assignee of the bug. > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.-- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists