| 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
| ||
|
Message-ID: <20061112133943.GB11484@elf.ucw.cz> Date: Sun, 12 Nov 2006 14:39:43 +0100 From: Pavel Machek <pavel@....cz> To: Eric Sandeen <sandeen@...deen.net> Cc: Steve Grubb <sgrubb@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] handle ext3 directory corruption better Hi! > >> 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. Yes... I played with similar tool few years ago on ext2, and it lead to fixing couple of bugs in e2fsck, too. vfat/reiser were too buggy for this test to be useful. > 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. Yes, that's what I did back then. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
Powered by blists - more mailing lists