linux-ext4 - Re: [PATCH] libext2fs: use ext2fs_blocks_count() in ext2fs

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] [day] [month] [year] [list]

Message-ID: <4A9F2CCA.8000307@redhat.com>
Date:	Wed, 02 Sep 2009 21:41:14 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Andreas Dilger <adilger@....com>
CC:	Justin Maggard <jmaggard10@...il.com>, nicholas.dokos@...com,
	ext4 development <linux-ext4@...r.kernel.org>,
	Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH] libext2fs: use ext2fs_blocks_count() in ext2fs_open2()

Andreas Dilger wrote:
> On Sep 02, 2009  17:33 -0500, Eric Sandeen wrote:
>> Justin Maggard wrote:
>>> On Wed, Sep 2, 2009 at 2:43 PM, Eric Sandeen<sandeen@...hat.com> wrote:
>>>> You guys are still getting bad checksums?
>>> Yeah, I am.
>> Oh, sorry, all the other bugs gave me a head-fake, and I forgot the
>> original problem of -fsck- corrupting the checksums.  :)  I had a simple
>> mkdir giving me the corruptions.  Ok, on to that.
> 
> I found the source of the checksum error last night - the reserved bytes
> in the 64-bit group descriptor are not zero after the e2fsck is run.
> It should be pretty easy to run e2fsck under gdb and put a hardware watch
> on those bytes to see who twiddles them.

Thanks, I saw that email a bit late today, will take a look.

-Eric

> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.

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