linux-kernel - Re: [PATCH] handle ext3 directory corruption better

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]

Message-ID: <4554E7C1.1070705@sandeen.net>
Date:	Fri, 10 Nov 2006 14:57:37 -0600
From:	Eric Sandeen <sandeen@...deen.net>
To:	Steve Grubb <sgrubb@...hat.com>
CC:	Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] handle ext3 directory corruption better

Steve Grubb wrote:
> On Tuesday 31 October 2006 04:57, Pavel Machek wrote:
>> Nice... can you run the same tool against fsck, too?
> 
> I'll see if I can make that work, too. The fuzzer tries to preserve the bad 
> image so that you can replay the problem for debugging. I think its just a 
> matter of making another copy and using that one instead.

I played with this on xfs a little bit in my spare time, found some
xfs_repair problems.  :)  I'm sure other fs's would have issues as well.

Ideally it would probably be good for the tool to have a "use" mode (try
to use the corrupted fs) and a "check" mode (try to fsck the corrupted fs).

In use   mode, it'd be:  mkfs, fuzz, mount, populate (etc), unmount.
In check mode, it'd be:  mkfs, mount, populate, unmount, fuzz, fsck.

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/