linux-ext4 - Re: [PATCH] make ext4_valid_block

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:	Mon, 15 Nov 2010 10:21:12 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Bernd Schubert <bs_lists@...ef.fastmail.fm>
CC:	linux-ext4@...r.kernel.org, Bernd Schubert <bschubert@....com>,
	Andreas Dilger <andreas.dilger@...cle.com>
Subject: Re: [PATCH] make ext4_valid_block_bitmap() more verbose

On 11/12/10 5:26 PM, Bernd Schubert wrote:
> The real issue we want to debug with the patch below actually came up while 
> stress testing Lustre using the RHEL5.5 kernel (so 2.6.32'ish ext4), but a 
> more verbose error function should not hurt for vanilla ext4 either.
> 
> make ext4_valid_block_bitmap() more verbose
> 
> While running our stress test suite, ext4_valid_block_bitmap() 
> frequently complains about an invalid block bitmap.
> However, e2fsck does not find anything. So in oder to be able
> to better debug this issue, make the function more verbose and 
> let it complain about the two possible invalid bitmaps.

Making a raw e2image of the problematic filesystem would let us take a
look at why e2fsck isn't finding problems; unless you plan to fix that
yourself as well, which is just fine of course.  :)

-Eric
 
> Signed-off-by: Bernd Schubert <bschubert@....com>
--
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