From: Eric Sesterhenn <snakebyte@gmx.de>
To: linux-fsdevel@vger.kernel.org
Subject: Filesystem fuzzing
Date: Mon, 19 May 2008 12:07:37 +0200 [thread overview]
Message-ID: <20080519100737.GA7764@alice> (raw)
hi,
i do some regular filesystem fuzzing, based on a modified version
of lmhs fsfuzzer. I try to test current -git at least once a week.
Most modifications are adding of new filesystems or mounting
them with different options, but i also added
some new tests like invoking iozone, fsx or fsstress if available
I currently test vfat, udf, msdos, swap, iso9660, ext2,
ext3, ext4, hfs, hfsplus, gfs2, ntfs, minix, qnx4, affs and bfs
I am not testing reiserfs and xfs since i dont even remotely have
a chance to get a clue when looking at the code, if someone maintaining
one of those filesystems is interested in oops reports please let me know.
Cramfs is not getting tested since it tends to end in long loops
with lots of warnings. I can only test on a 32bit x86 box at the
moment, so it might be interesting if someone runs this stuff on some
64bit box or other architecture.
The current, modified version of the fuzzer can be found here
http://www.cccmz.de/~snakebyte/fsfuzzer-0.6-lmh2.tar.bz2
To test bfs you need to put the bfs example files from
http://sourceforge.net/project/showfiles.php?group_id=39575 into
an images/ subdirectory. Same goes for hpfs with the file
from http://sourceforge.net/project/showfiles.php?group_id=39575
and for adf you need bubblebobble.adf (not sure if i am
allowed to link or redistribute this)
If someone can point me to an mkfs tool for bfs, hpfs or
adf i would be thankful.
Same goes for vxfs, if someone has an image or a tool
to create images this would be helpful.
If someone has additional ideas what one could check, please
let me know :-)
At the moment the only oopses i see are with bfs and hfs,
if you are interested please take a look
http://kerneloops.org/raw.php?rawid=10088&msgid=
http://kerneloops.org/raw.php?rawid=11232&msgid=
I still have the images and can reproduce and try patches.
for the hfs one, there is similar code in hfs+ but with
a check to prevent this, triggering a warn and an oops later
if i try to port this to hfs.
Greetings, Eric
next reply other threads:[~2008-05-19 10:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 10:07 Eric Sesterhenn [this message]
2008-05-20 15:40 ` Filesystem fuzzing Dave Kleikamp
2008-05-21 8:26 ` Eric Sesterhenn
[not found] ` <20080521111627.GA14265@alice>
2008-05-21 15:10 ` Eric Sesterhenn
2008-05-21 16:19 ` Dave Kleikamp
2008-05-21 15:44 ` Dave Kleikamp
2008-05-22 20:29 ` Eric Sesterhenn
2008-05-21 17:21 ` Sunil Mushran
2008-05-21 18:49 ` Eric Sesterhenn
2008-05-27 8:00 ` Eric Sesterhenn
2008-05-27 8:29 ` Eric Sesterhenn
2008-05-28 2:29 ` Sunil Mushran
2008-05-29 13:17 ` Eric Sesterhenn
2008-05-29 14:56 ` Szabolcs Szakacsits
2008-05-30 7:51 ` Eric Sesterhenn
2008-05-30 19:58 ` Szabolcs Szakacsits
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=20080519100737.GA7764@alice \
--to=snakebyte@gmx.de \
--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).