From: Eric Sesterhenn <snakebyte@gmx.de>
To: Szabolcs Szakacsits <szaka@ntfs-3g.org>
Cc: linux-fsdevel@vger.kernel.org, ntfs-3g-devel@lists.sf.net
Subject: Re: Filesystem fuzzing
Date: Fri, 30 May 2008 09:51:28 +0200 [thread overview]
Message-ID: <20080530075128.GB14540@alice> (raw)
In-Reply-To: <Pine.LNX.4.61.0805291711151.31472@dhcppc2>
Hi,
* Szabolcs Szakacsits (szaka@ntfs-3g.org) wrote:
>
> We added ntfs-3g and fuse support, fixed the one crash and three hang
> problems it found and made a new stable ntfs-3g 1.2531 release available:
>
> http://ntfs-3g.org/
>
> The fsfuzzer patch is attached below, it includes
>
> - fixes for potentially leaking loop device
> - simplification for mkntfs which can be used on files
> - ntfs-3g and fuse support
nice, i added them to my lokal version
> > if someone maintaining one of those filesystems is interested in oops
> > reports please let me know.
>
> We would appreciate ntfs-3g testing a lot. FUSE is used by over a hundred
> file systems and ntfs-3g by many users, devices.
>
> > 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.
>
> We are using fsfuzz on x86_64 too and hopefully soon on big-endian MIPS
> and ARM.
nice, to you only use those to test fuse/ntfs-3g or
also the other filesystems?
> If you have any question, problem then we'd be happy to answer and help any
> time.
>
> This tool is really great. It will be very useful for hot-repair testing as
> well in the future :-)
yeah, lmh did some nice job for the month of kernel bugs
I added ntfs-3g testing to my testbox, and use the mercurial tree
from http://mercurial.creo.hu/repos/ntfs-3g-hg to always test
the latest version. The only problem I have is that when
i mount images with -t ntfs the fuse driver also gets
used, not the kernel one. is there an option to only use
ntfs-3g when using -t ntfs-3g?
Greetings, Eric
next prev parent reply other threads:[~2008-05-30 7:51 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
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 [this message]
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=20080530075128.GB14540@alice \
--to=snakebyte@gmx.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ntfs-3g-devel@lists.sf.net \
--cc=szaka@ntfs-3g.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).