On Thu, Jan 22, 2009 at 12:12:01PM +0100, Eric Sesterhenn wrote: > * Eric Sesterhenn (snakebyte@xxxxxx) wrote: > > 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. Thanks, they were all traced to the superblock parameter s_first_ino being extremely large --- much larger than s_inodes_count. I've committed the following patches to address the problem at multiple levels. - Ted -- 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
