public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [patch] xfs/259 - inherit $_fs_has_crcs
Date: Fri, 04 Dec 2015 15:56:56 -0500	[thread overview]
Message-ID: <x49egf23pbb.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20151204204557.GA64533@bfoster.bfoster> (Brian Foster's message of "Fri, 4 Dec 2015 15:45:57 -0500")

Brian Foster <bfoster@redhat.com> writes:

>> > @@ -72,7 +72,7 @@ for del in $sizes_to_check; do
>> >  	lofile=$(losetup -f)
>> >  	losetup $lofile "$testfile"
>> >  	"$MKFS_XFS_PROG" -l size=32m -b size=$blocksize $lofile \
>> > -					>/dev/null || echo "mkfs failed!"
>> > +			 -m crc=$_fs_has_crcs>/dev/null || echo "mkfs failed!"
>> 
>> It occurs to me that this may break on systems using a mkfs.xfs that
>> does not support the "-m crc" option.  Is there a standard way to test
>> for such things?
>> 
>
> I suppose we could add a $crc_options to the mkfs command line that can
> be set appropriately in the if/else. If the test fs has crc support, set
> crc_options="-m crc=1". Otherwise, maybe use
> '_scratch_mkfs_xfs_supported -m crc=0' (from
> common/rc:_require_xfs_mkfs_crc()) in the else condition to either set
> crc_options="-m crc=0" or drop the option (crc_options="")?

How does one determine whether mkfs.xfs supports the crc= option?  That
was the question I tried to ask.  ;-)

> Another option could be just to unconditionally set crc=[0|1] and add a
> _require_xfs_crc() to the test, but that would just skip the test on
> older systems.

I think we can agree that would be a bad approach.  :)

-Jeff

  reply	other threads:[~2015-12-04 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 15:41 [patch] xfs/259 - inherit $_fs_has_crcs Jeff Moyer
2015-12-04 15:47 ` Jeff Moyer
2015-12-04 20:45   ` Brian Foster
2015-12-04 20:56     ` Jeff Moyer [this message]
2015-12-05  8:09       ` 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=x49egf23pbb.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=bfoster@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