From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Anna Schumaker <Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
fstests-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Lukas Czerner <lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: xfstests and linux nfs testing
Date: Thu, 9 Oct 2014 09:21:27 -0700 [thread overview]
Message-ID: <20141009162127.GA12500@infradead.org> (raw)
In-Reply-To: <54368292.8060209-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
On Thu, Oct 09, 2014 at 08:41:54AM -0400, Anna Schumaker wrote:
> I think this is a bug in xfstests. This fixes it for me, but I'm not sure what needs to be checked in the NFS case:
Lukas broke this with:
common: Check fs consistency on TEST_DEV only when needed
as far as I can tell it blindly copied the _require_scratch code
to _require_test, which is bad for two reasons:
a) due to lots of code duplication
b) because it broke filesystems that don't support a scratch dev
like nfs.
Anna fix should work, can you resend it to the fstests lists with a
proper signoff? Even better would be some validation that the
passed in "device" is a valid format for a nfs export, but that's not
strictly required.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-09 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 3:09 xfstests and linux nfs testing Steve French
[not found] ` <CAH2r5mt8EfVraedY2Gi31E4xQG=p=YqtAXEoH2a+FYHdmBzbqA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-09 12:41 ` Anna Schumaker
[not found] ` <54368292.8060209-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2014-10-09 16:21 ` Christoph Hellwig [this message]
[not found] ` <20141009162127.GA12500-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-10-09 17:36 ` Anna Schumaker
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=20141009162127.GA12500@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=fstests-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).