From: "Theodore Ts'o" <tytso@mit.edu>
To: Valerie Henson <val_henson@linux.intel.com>,
Andrew Morton <akpm@osdl.org>,
pbadari@gmail.com, linux-kernel@vger.kernel.org,
Ext2-devel@lists.sourceforge.net, arjan@linux.intel.com,
zach.brown@oracle.com
Subject: Re: [Ext2-devel] [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit]
Date: Fri, 24 Mar 2006 16:39:05 -0500 [thread overview]
Message-ID: <20060324213905.GG18020@thunk.org> (raw)
In-Reply-To: <20060324210033.GQ14852@schatzie.adilger.int>
On Fri, Mar 24, 2006 at 02:00:33PM -0700, Andreas Dilger wrote:
> > This would be a prime candidate for trying to add the same sort of
> > userspace test framework which Rusty and company did for netfilter, so
> > we can try to test for race conditions, corner cases, etc.
>
> Are you saying to make a filesystem test harness in userspace, or to
> add hooks into the kernel to trigger specific cases in the running
> kernel?
The former: a filesystem test harness in userspace, possibly with some
kernel code changes to make it easier to integrate it with the
userspace test harness. It's very similar to what the Netfilter folks
did, and it has the advantage that we can do testing much more
quickly, especially in cases where we want to simulate crashes at
certain specific test points to make sure the journal recovery happens
correctly.
- Ted
next prev parent reply other threads:[~2006-03-24 21:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 1:10 [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit] Valerie Henson
2006-03-22 8:40 ` Valerie Henson
2006-03-22 13:08 ` Alan Cox
2006-03-22 18:18 ` [Ext2-devel] " Mingming Cao
2006-03-22 18:16 ` [Ext2-devel] " Mingming Cao
[not found] ` <200603230011.53793.ioe-lkml@rameria.de>
2006-03-22 23:52 ` Mingming Cao
2006-03-22 19:09 ` Badari Pulavarty
2006-03-22 22:48 ` Valerie Henson
2006-03-23 1:55 ` Andrew Morton
2006-03-24 14:32 ` Valerie Henson
2006-03-24 15:35 ` Dave Kleikamp
2006-03-24 18:48 ` Andrew Morton
2006-03-24 19:13 ` Mingming Cao
2006-03-24 19:31 ` Andreas Dilger
2006-03-24 18:52 ` Theodore Ts'o
2006-03-24 19:14 ` Mingming Cao
2006-03-24 19:28 ` Andreas Dilger
2006-03-24 20:01 ` Theodore Ts'o
2006-03-24 21:00 ` Andreas Dilger
2006-03-24 21:39 ` Theodore Ts'o [this message]
2006-03-24 22:16 ` Andreas Dilger
2006-03-25 5:13 ` Suparna Bhattacharya
2006-03-25 17:38 ` Ben Pfaff
2006-03-24 20:52 ` [Ext2-devel] " Matthew Wilcox
2006-03-24 21:23 ` Andreas Dilger
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=20060324213905.GG18020@thunk.org \
--to=tytso@mit.edu \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=val_henson@linux.intel.com \
--cc=zach.brown@oracle.com \
/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