As suggested by pavel i tested how e2fsck handles corrupted images, I used the fuzzer bunny (http://code.google.com/p/bunny-the-fuzzer/) At http://www.cccmz.de/~snakebyte/e2fsck_err.tar.bz2 you can find a bunch of images crashing e2fsck or keeping it in an endless loop. I tested with e2fsck 1.41.0 which was the one i had at hand. The crashes are either in ext2fs_inode_alloc_stats2() or ext2fs_read_inode_full(), looks like those are always the same faults. 000 endless loop 000 endless loop 053 ext2fs_inode_alloc_stats2 054 ext2fs_inode_alloc_stats2 073 different endless loop? 086 ext2fs_inode_alloc_stats2 112 ext2fs_read_inode_full 139 ext2fs_inode_alloc_stats2 143 ext2fs_inode_alloc_stats2 161 ext2fs_inode_alloc_stats2 192 ext2fs_inode_alloc_stats2 209 ext2fs_inode_alloc_stats2 214 endless loop 216 ext2fs_read_inode_full 241 endless loop 266 endless loop 303 ext2fs_inode_alloc_stats2 389 ext2fs_inode_alloc_stats2 438 ext2fs_inode_alloc_stats2 440 endless loop 446 ext2fs_inode_alloc_stats2 449 ext2fs_read_inode_full 451 ext2fs_read_inode_full 455 ext2fs_read_inode_full 518 ext2fs_inode_alloc_stats2 530 ext2fs_inode_alloc_stats2 534 ext2fs_inode_alloc_stats2 Greetings, Eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
