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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 22 Jun 2007 10:04:54 -0600
From:	Andreas Dilger <>
To:	Avantika Mathur <>
Cc:	Girish Shilamkar <>,
Subject: Re: [PATCH] uninitialized groups ported - kernel

On Jun 21, 2007  16:54 -0700, Avantika Mathur wrote:
> Kernel build was failing with the uninitialized patches when 
> CONFIG_CRC16=m. The patch below resolves this issue.

No patch?

> Also, when testing the patches, filesystem mount fails:
> EXT4-fs error (device sdc1): ext4_check_descriptors: Checksum for group 1 
> failed (0!=1)
> EXT4-fs: group descriptors corrupted!
> EXT4-fs error (device sdc1): ext4_check_descriptors: Checksum for group 7 
> failed (0!=1)
> Even though the uninitgrps feature is not enabled, the gdp->bg_checksum 
> on disk is nonzero.

Can you figure out why the on-disk checksum is non-zero?  That should not
happen.  Is it possible that the kernel patch and e2fsprogs somehow have
the wrong struct alignment?  Is mke2fs not zeroing out the on-disk data -
the error is reporting that bg_checksum on disk is 1 when it should be 0?

I suppose it is possible for the patch to just ignore the on-disk data if
checksums are not enabled, but we didn't have any such problems in the past...

Cheers, Andreas
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists