From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Eryu Guan <eguan@redhat.com>, fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs/259: handle minimum block size more precisely
Date: Thu, 7 Apr 2016 16:48:37 -0700 [thread overview]
Message-ID: <20160407234837.GA1439@infradead.org> (raw)
In-Reply-To: <20160407213231.GD761@dastard>
On Fri, Apr 08, 2016 at 07:32:31AM +1000, Dave Chinner wrote:
> > diff --git a/tests/xfs/259 b/tests/xfs/259
> > index 16c1935..3150ff3 100755
> > --- a/tests/xfs/259
> > +++ b/tests/xfs/259
> > @@ -51,9 +51,7 @@ testfile=$TEST_DIR/259.image
> > # Test various sizes slightly less than 4 TB. Need to handle different
> > # minimum block sizes for CRC enabled filesystems, but use a small log so we
> > # don't write lots of zeros unnecessarily.
> > -xfs_info $TEST_DIR | _filter_mkfs 2> $tmp.mkfs > /dev/null
> > -. $tmp.mkfs
>
> This tests the configuration of the test device, which is not
> controlled by the test harness, so can be different to the
> configuration being used for the scratch device.
>
> > -if [ $_fs_has_crcs -eq 1 ]; then
> > +if [ $XFS_MKFS_CRC_DEFAULT -eq 1 ]; then
>
> IOWs, this is not an not equivalent test.
And I think that's the whole point of this change :)
Previously it tested what the TEST_DIR did, which was wrong for this
test. Now it tests what mkfs does by default (including for the scratch
dev), which is what we really want here.
next prev parent reply other threads:[~2016-04-07 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 11:05 [PATCH] xfs/259: handle minimum block size more precisely Eryu Guan
2016-04-07 15:46 ` Christoph Hellwig
2016-04-07 21:32 ` Dave Chinner
2016-04-07 23:48 ` Christoph Hellwig [this message]
2016-04-11 0:02 ` Dave Chinner
2016-04-11 3:12 ` Eryu Guan
2016-04-11 11:38 ` Eryu Guan
2016-04-12 21:01 ` Dave Chinner
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=20160407234837.GA1439@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--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