linux-ext4 - ext3_valid_block_bitmap: Invalid block bitmap in 2.6.25rc in memory

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

Message-ID: <20080412205714.GA6855@basil.nowhere.org>
Date:	Sat, 12 Apr 2008 22:57:15 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	linux-ext4@...r.kernel.org
Subject: ext3_valid_block_bitmap: Invalid block bitmap in 2.6.25rc in memory


FYI, a system here running various 2.6.25rc kernels (latest upto rc7-git6) 
with longer uptimes suddenly decided to fsck one of its file systems
due to an error after reboot.

The error causing this was:

kernel: EXT3-fs error (device dm-0): ext3_valid_block_bitmap: Invalid block bitmap - block_group = 285, block = 9338882

detected by the 2.6.25rc7-git6 kernel.

I don't see any ill effects from it and fsck didn't find anything wrong
so it must have been something spurious in memory only (or fsck
fails to check for this condition, but that is hard to imagine) 

The system never showed anything like this on earlier kernel versions.

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