All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Dave Jones <davej@redhat.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org, Eric Sandeen <esandeen@redhat.com>,
	Subrata Modak <subrata@linux.vnet.ibm.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Updated fsx.c program (fixed fallocate)
Date: Wed, 30 Sep 2009 11:47:59 -0500	[thread overview]
Message-ID: <4AC38BBF.4080707@redhat.com> (raw)
In-Reply-To: <20090930161913.GA3425@redhat.com>

Dave Jones wrote:
> On Wed, Sep 30, 2009 at 10:32:37AM -0500, Eric Sandeen wrote:
>  > Randy Dunlap wrote:
>  > > On Tue, 29 Sep 2009 16:39:38 -0600 Andreas Dilger wrote:
>  > > 
>  > >> I've done some work to merge some of the existing fsx.c mods into a
>  > >> single version.  Over & above the version that is in the LTP, I've
>  > >> included AKPM's O_DIRECT fixes (with a twist), the BSD mmap page and
>  > >> segfault handling, and per-write fsync.
>  > > 
>  > > It sure would be Good if fsx-linux had a fixed, known home, instead of
>  > > having to look at Andrew's ext3-tools, Dave's codemonkey files,
>  > > LTP, linux-fsdevel mailing list, etc.
>  > > 
>  > > Is there a linux-fs-tests package somewhere?  (like where the xfstests
>  > > are being merged into)
>  > 
>  > Well, I think Andreas' idea was to make LTP the official home for now 
>  > which is why I was going to send it here ...
>  > 
>  > But I don't think xfstests is being merged into anything at the moment; 
>  > if anything, we're working to make it a more generic suite of tests (it 
>  > can run about 50 tests on generic posix filesystems by now).
> 
> I'd love to see a tests/ directory shipped with the kernel.
> It's been talked about for about several years and still hasn't happened.
> 
> Is it just because no-one has stepped up to do it ?
> I would be happy to manage a git tree for marshalling stuff on its way to Linus
> if that's all that's holding this idea back.
> 
> Of course if there are other objections..
> 
> 	Dave
>  

Perhaps for simple, small things like fsx.c that might make sense, but a 
full-blown test suite could add significantly to the size of the tarball 
I'd think (especially by the time you start including things like 
including pre-corrupted images, perhaps)...

-Eric



  reply	other threads:[~2009-09-30 16:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  5:25 Updated fsx.c program Andreas Dilger
2009-09-29 21:38 ` Andreas Dilger
2009-09-29 22:39   ` Updated fsx.c program (fixed fallocate) Andreas Dilger
2009-09-30  3:34     ` Eric Sandeen
2009-09-30 15:21     ` Randy Dunlap
2009-09-30 15:32       ` Eric Sandeen
2009-09-30 16:19         ` Dave Jones
2009-09-30 16:47           ` Eric Sandeen [this message]
2009-10-02 22:37     ` Mingming
2009-10-02 22:40       ` Eric Sandeen
2009-10-02 23:26         ` Mingming
2009-10-03  2:40           ` Nick Dokos
2009-10-03  3:40             ` Eric Sandeen

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=4AC38BBF.4080707@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=davej@redhat.com \
    --cc=esandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=subrata@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.