From: Greg KH <greg@kroah.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Filesystem Mutation Tool
Date: Fri, 4 Aug 2006 23:48:41 -0700 [thread overview]
Message-ID: <20060805064841.GA26458@kroah.com> (raw)
In-Reply-To: <44D3FD46.7070805@us.ibm.com>
On Fri, Aug 04, 2006 at 07:07:02PM -0700, Darrick J. Wong wrote:
> Hi all,
>
> As I might've mentioned to a few of you at OLS, I've hacked up a quick
> and dirty program to study the effects of what happens to a filesystem
> when certain blocks mutate underneath it (think malice, your RAID5
> controller goes berserk, etc). Said program is now posted in a crude
> form here:
>
> http://sweaglesw.net/~djwong/programs/fs_mutate/
>
> I've run this program against ext3 and reiserfs; so far, ext3 seems to
> be the stability winner, as it tends to stay up the longest (about 30-35
> minutes) even with destroy mode turned on. reiserfs lasts a few minutes
> under such a beating. Of course, "stays up" is a long way from "works
> properly" -- overwriting things like indirect blocks has the rather
> amusing effect of generating lots of messages about falling off the end
> of a drive. As with the folks who used carefully crafted ISO9660
> filesystems to crash arbitrary machines demonstrated last year, it's not
> so hard to get Linux to automount filesystems. To my knowledge,
> nobody's tried a similar thing against the other filesystems, though I
> could just be ignorant.
People have done it in the past, and found lots of bugs that have
hopefully been fixed (although the iso issues have not been fixed...)
> What do you think? Useful tool? Or am I the one being the tool? ;)
I think it's useful, especially if it causes things to be fixed up in
the kernel :)
Try running it against a vfat filesystem and see if you can create some
good oopses. That would be a good place to start, as USB flash sticks
are more common these days than cdroms...
thanks,
greg k-h
prev parent reply other threads:[~2006-08-05 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 2:07 Filesystem Mutation Tool Darrick J. Wong
2006-08-05 6:48 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060805064841.GA26458@kroah.com \
--to=greg@kroah.com \
--cc=djwong@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).