public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Pfaff <blp@cs.stanford.edu>
To: linux-kernel@vger.kernel.org
Cc: ext2-devel@lists.sourceforge.net
Subject: Re: [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit]
Date: Sat, 25 Mar 2006 09:38:26 -0800	[thread overview]
Message-ID: <8764m2v2zx.fsf@benpfaff.org> (raw)
In-Reply-To: 20060324221656.GW14852@schatzie.adilger.int

Andreas Dilger <adilger@clusterfs.com> writes:

> On Mar 24, 2006  16:39 -0500, Theodore Ts'o wrote:
>> 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.
>
> I seem to recall that the Stanford Metacompilation group (Dawson Engler)
> already wrote such a tool.  Not sure what sort of access there is for the
> tool, whether public funding would grant access to the public, or if they
> are at least willing to make an online interface available (the group has
> spun out into "Coverity", and it seems unlikely it will be completely OSS).

I know the guys who wrote FiSC, the tool in question, and I have
even hacked on related software a little bit myself.  I suspect
that, if asked, they would say that the code is rather
embarrassing and that they wouldn't want to release it for that
reason.  However, to my knowledge it wasn't written by or in
conjunction with Coverity, so there wouldn't be any issues of
that kind.

If you want to pursue this, I'd recommend emailing Paul Twohey
<twohey@CS.Stanford.EDU> or Junfeng Yang <yjf@stanford.edu>.  As
I understand it, they are the grad students who spent the most
time working on FiSC and related tools.
-- 
Ben Pfaff 
email: blp@cs.stanford.edu
web: http://benpfaff.org


  parent reply	other threads:[~2006-03-25 17:38 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
2006-03-24 22:16                 ` Andreas Dilger
2006-03-25  5:13                   ` Suparna Bhattacharya
2006-03-25 17:38                   ` Ben Pfaff [this message]
2006-03-24 20:52           ` 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=8764m2v2zx.fsf@benpfaff.org \
    --to=blp@cs.stanford.edu \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@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