From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs mailing list <xfs@oss.sgi.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] xfstests: enable many tests to run on ext2/3/4
Date: Sun, 24 May 2009 10:39:46 -0400 [thread overview]
Message-ID: <20090524143945.GA32554@infradead.org> (raw)
In-Reply-To: <4A15B649.70801@redhat.com>
Wow, that's a nice start. The only important thing missing is checking
the filesystems after each test run for the non-xfs case.
Maybe we should put this in in stages? The _supported_fs generic
thing is a nice cleanup already for the existing xfs/nfs/udf setup
and should go in ASAP.
The _scratch_mkfs output fix in 069 could also be a separate patch.
The _setup_generic_testdir should be generalized to match XFS for the
default case and just set testdir in _setup_testdir instead of
another function. Also the comment there should be updated.
Same for _cleanup_testdir.
Btw, the way udf and nfs are currently handled look not very nice to me.
We should not set up the test device by default for any filesystem but
rather have a -setup or similar option to set it up if needed.
In common I would indeed prefer a new fstype option, but we might aswell
put the current version in as-is. Especially if we could tie up a really
generic fstype= that wouldn't require listing the filesystems if they
don't require special mount options or similar.
The only thing preventing that is as far as I can see the current difference
in _require_scratch for xfs and udf vs the rest. Which looks really weird
to me, need to investigate what's going on.
As for the generic group I must say I don't like it very much, the
filtering of notrun (maybe only notrun because of the filesystem type
mismatch) sounds much better to me.
next prev parent reply other threads:[~2009-05-24 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 20:15 [PATCH] xfstests: enable many tests to run on ext2/3/4 Eric Sandeen
2009-05-24 14:39 ` Christoph Hellwig [this message]
2009-05-24 16:38 ` Eric Sandeen
2009-05-25 15:31 ` 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=20090524143945.GA32554@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).