From: Dave Chinner <david@fromorbit.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, jtulak@redhat.com
Subject: Re: [PATCH v2] xfs/191: skip tests on older xfsprogs
Date: Thu, 18 Aug 2016 11:04:10 +1000 [thread overview]
Message-ID: <20160818010410.GB22388@dastard> (raw)
In-Reply-To: <1471409161-28510-1-git-send-email-yangx.jy@cn.fujitsu.com>
On Wed, Aug 17, 2016 at 12:46:01PM +0800, Xiao Yang wrote:
> If we don't have /tmp/foo file on xfsprogs 3.2.2, _require_xfs_mkfs_validation
> will fail because mkfs.xfs can't create this file. We need to skip tests
> before xfsprogs 4.7.0, so fix it. the feature has been introduced since
> xfsprogs 4.2.0:
> commit 20cec860e16b267ea0c71a2f648fa2b26aad2e65
> Author: Eric Sandeen <sandeen@sandeen.net>
> Date: Fri Jul 31 09:04:11 2015 +1000
> mkfs.xfs: always use underlying fs sector size when mkfs'ing a file
>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
> ---
> common/rc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/common/rc b/common/rc
> index b19b698..1907c70 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -3889,6 +3889,7 @@ _get_fs_sysfs_attr()
> # number of failed cases.
> _mkfs_validation_check()
> {
> + touch /tmp/foo >/dev/null 2>&1
> local cmd="$MKFS_XFS_PROG -f -N -d file,name=/tmp/foo,size=$((1024 * 1024 * 1024))"
> $cmd -s size=2s >/dev/null 2>&1
> local sum=$?
Couple of things here:
1. this is an xfs specific check. The function needs to have
"xfs" in it's name. i.e. _xfs_mkfs_validation_check
2. Don't hard code temporary files ie use mktemp for
creating the file like so:
imgfile=`mktemp`
.....
rm -f $imgfile
3. mkfs.xfs takes human readable units for sizes, such as
"1g" for a 1GB filesystem and "260k" for the log size. No
need calculations in the script for this, and this gets
rid of overly long lines and makes it easier to read.
4. Whitespace between each check and result processing makes
it much easier to see each of the operations being
performed during the check.
i.e.
_xfs_mkfs_validation_check()
{
local imgfile=`mktemp`
local cmd="$MKFS_XFS_PROG -f -N -d file,name=/tmp/foo,size=1g"
$cmd -s size=2s >/dev/null 2>&1
local sum=$?
$cmd -l version=2,su=260k >/dev/null 2>&1
sum=`expr $sum + $?`
rm -f $imgfile
return $sum
}
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-08-18 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 3:18 [PATCH] xfs/191: skip tests on older xfsprogs Xiao Yang
2016-08-17 3:36 ` Eryu Guan
2016-08-17 4:46 ` [PATCH v2] " Xiao Yang
2016-08-18 1:04 ` Dave Chinner [this message]
2016-08-18 3:09 ` [PATCH v3] " Xiao Yang
2016-08-17 9:27 ` [PATCH] " Jan Tulak
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=20160818010410.GB22388@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jtulak@redhat.com \
--cc=yangx.jy@cn.fujitsu.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