linux-ext4 - Re: [Bug 42859] New: kernel BUG at fs/ext4/extents.c:1953

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]

Date:	Sun, 4 Mar 2012 20:51:21 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Matthias Erll <merll@....de>
Cc:	linux-ext4@...r.kernel.org, bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 42859] New: kernel BUG at fs/ext4/extents.c:1953

On Sun, Mar 04, 2012 at 11:11:00PM +0100, Matthias Erll wrote:
> 
> In the three cases I can reproduce, the inode number has been identical.
> Please find the debugfs output below.

Thanks, this is helpful.  It is indeed a bug in e2fsck; it's not
noticing the case where the extent length is zero (but the extent
header was still valid).  The workaround is to run the following
commands with the file system unmounted:

# debugfs -w -R "clri <1312385>" /dev/sda2
# e2fsck -f /dev/sda2

I'll get this fixed in the next maintenance release of e2fsprogs.

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