[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090122111201.GA32200@alice>
Date: Thu, 22 Jan 2009 12:12:01 +0100
From: Eric Sesterhenn <snakebyte@....de>
To: pavel@...e.cz, tytso@....edu
Cc: linux-ext4@...r.kernel.org
Subject: Re: e2fsck faults with corrupted images
* Eric Sesterhenn (snakebyte@....de) 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.
I just tried again with e2sck 1.41.3 and I can still
produce the errors.
Greetings, Eric
--
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
Powered by blists - more mailing lists