linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
	Michael Rubin <mrubin@google.com>,
	Eric Sandeen <sandeen@redhat.com>,
	linux-ext4@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?
Date: Tue, 15 Feb 2011 12:29:22 -0500	[thread overview]
Message-ID: <20110215172922.GG4255@thunk.org> (raw)
In-Reply-To: <20110215042837.GD13052@dastard>

On Tue, Feb 15, 2011 at 03:28:37PM +1100, Dave Chinner wrote:
> 
> What scripts are needed? xfstests has the $MKFS_OPTIONS and
> $MOUNT_OPTIONS environment variables for customising your mkfs and
> mount parameters for each test run, so isn't testing ext3
> filesystems with the ext4 code should just be a matter of setting
> these appropriately?

Correct, this doesn't require changes to xfstests.

What is needed for this ext4/ext3-using-ext4 testing is a wrapper
script *around* xfstests that sets up the enviornment variables
correctly, and uses different devices for the "common case"
combinations of mkfs and mount options (where we would keep an aged
file system around), and for those devices which we don't think are
valuable enough to dedicate a reserved file system image, we'd have to
mkfs a special version of that filesystem for TEST_DEV.

(I'm not sure why xfstests doesn't use freshly created file in the
case where SCRATCH_DEV is defined by TEST_DEV is not, but it doesn't;
as far as I know there are no tests where it uses both TEST_DEV and
SCRATCH_DEV, is there?)

							- Ted

  reply	other threads:[~2011-02-15 17:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 14:40 [LSF/MM TOPIC] Drop ext2/ext3 codebase? When? Jan Kara
2011-02-03 15:08 ` Eric Sandeen
2011-02-03 19:32   ` Michael Rubin
2011-02-03 19:49     ` Eric Sandeen
2011-02-03 21:57       ` Amir Goldstein
2011-02-03 22:00         ` Eric Sandeen
2011-02-04 13:59         ` Jan Kara
2011-02-04  0:04     ` Ted Ts'o
2011-02-04 13:17     ` Jan Kara
2011-02-04 17:03       ` Ric Wheeler
2011-02-04 17:17         ` [Lsf-pc] " James Bottomley
2011-02-05 18:43           ` Trond Myklebust
2011-02-07 17:21           ` Mingming Cao
2011-02-12 11:05       ` Amir Goldstein
2011-02-14 17:25         ` Jan Kara
2011-02-14 19:00           ` Amir Goldstein
2011-02-14 19:58             ` Ted Ts'o
2011-02-14 20:59               ` Andreas Dilger
2011-02-14 21:22               ` Amir Goldstein
2011-02-15  4:28               ` Dave Chinner
2011-02-15 17:29                 ` Ted Ts'o [this message]
2011-02-21 23:48                   ` Dave Chinner
2011-02-04 13:03   ` Jan Kara
2011-02-04 17:36     ` Andreas Dilger
2011-02-07 16:19       ` Jan Kara
2011-02-07 16:35         ` Andreas Dilger
2011-02-11 11:16           ` Jan Kara
2011-02-11 18:44             ` Michael Rubin

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=20110215172922.GG4255@thunk.org \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mrubin@google.com \
    --cc=sandeen@redhat.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).