From: "Theodore Ts'o" <tytso@mit.edu>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common: add support for the "local" file system type
Date: Wed, 28 Sep 2016 20:01:30 -0400 [thread overview]
Message-ID: <20160929000130.ixuytsr5euxef6vk@thunk.org> (raw)
In-Reply-To: <20160927095529.GO27776@eguan.usersys.redhat.com>
On Tue, Sep 27, 2016 at 05:55:29PM +0800, Eryu Guan wrote:
>
> It has nothing to do with mount & umount, it's about adding a new
> "-local" option to "check", like "-nfs" and "-overlay". And do
> TEST_DEV/TEST_DIR and SCRATCH_DEV/SCRATCH_MNT validations in
> _require_test and _require_scratch_nocheck, as how we do the check for
> NFS and overlayfs. So we don't have to work around the validation by
> specifying TEST_DEV/SCRATCH_DEV in a non-block device format (e.g.
> local:/test to mimic an NFS export).
I'd have to dig and check, but as I recall, there were assumptions
that foo:/bar means "no block device" scattered around, and it's why
we have to use a similar naming scheme for tmpfs. Is that really a
problem? I had thought it was a standard convention for xfstests.
If we want to avoid forcing testers to use a foo:/bar naming scheme
for TEST_DEV and SCRATCH_DEV, instead of a new command-line variable,
I'd much rather have a function in rc/common that could be keyed off
the file system type. You have to specify whether you are using tmpfs
or nfs or local in FSTYP anyway, so why not just use that?
Cheers,
- Ted
next prev parent reply other threads:[~2016-09-29 1:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 20:05 [PATCH] common: add support for the "local" file system type Theodore Ts'o
2016-09-26 13:25 ` Eryu Guan
2016-09-26 15:14 ` Theodore Ts'o
2016-09-27 9:55 ` Eryu Guan
2016-09-29 0:01 ` Theodore Ts'o [this message]
2016-09-26 22:18 ` Dave Chinner
2016-09-28 23:57 ` Theodore Ts'o
2016-09-29 2:16 ` Dave Chinner
2016-09-29 3:56 ` Theodore Ts'o
2016-09-29 5:37 ` Dave Chinner
2016-09-29 13:05 ` Theodore Ts'o
2016-09-29 22:49 ` Dave Chinner
2016-09-30 3:43 ` Theodore Ts'o
2016-09-29 13:37 ` Eric Sandeen
2016-09-29 13:57 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2018-05-03 3:43 Theodore Y. Ts'o
2018-05-03 9:22 ` Amir Goldstein
2018-05-03 18:35 ` Theodore Y. Ts'o
2018-05-03 19:24 ` Amir Goldstein
2018-05-06 3:54 ` Eryu Guan
2018-05-12 8:42 ` Eryu Guan
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=20160929000130.ixuytsr5euxef6vk@thunk.org \
--to=tytso@mit.edu \
--cc=eguan@redhat.com \
--cc=fstests@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