linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sesterhenn <snakebyte@gmx.de>
To: Sunil Mushran <Sunil.Mushran@oracle.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Filesystem fuzzing
Date: Wed, 21 May 2008 20:49:43 +0200	[thread overview]
Message-ID: <20080521184943.GA16760@alice> (raw)
In-Reply-To: <48345A30.9030004@oracle.com>

* Sunil Mushran (Sunil.Mushran@oracle.com) wrote:
> Eric Sesterhenn wrote:
>> 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
>
> Please can you add ocfs2 to the mix. To make it easy, you
> can format with "mkfs.ocfs2 -M local" to mark the volume
> for local mount only and thus not deal with any cluster config.

sure. might take some days until i find the time to do this,
but if any bugs pop up i'll let you know.

greetings, Eric

  reply	other threads:[~2008-05-21 18:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 10:07 Filesystem fuzzing Eric Sesterhenn
2008-05-20 15:40 ` 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 [this message]
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=20080521184943.GA16760@alice \
    --to=snakebyte@gmx.de \
    --cc=Sunil.Mushran@oracle.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).