From: Eryu Guan <guaneryu@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests <fstests@vger.kernel.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: test packaged crc32c code
Date: Sat, 3 Nov 2018 23:38:03 +0800 [thread overview]
Message-ID: <20181103153803.GB12788@desktop> (raw)
In-Reply-To: <20181029181242.GA4131@magnolia>
On Mon, Oct 29, 2018 at 11:12:42AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Use the new crc32selftest command in xfs_io to check the correct
> operation of the packaged xfsprogs, on the off chance that the packages
> were cross compiled on a different machine type (which means the build
> time test doesn't hold much water).
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> tests/xfs/734 | 44 ++++++++++++++++++++++++++++++++++++++++++++
> tests/xfs/734.out | 3 +++
> tests/xfs/group | 1 +
> 3 files changed, 48 insertions(+)
> create mode 100755 tests/xfs/734
> create mode 100644 tests/xfs/734.out
>
> diff --git a/tests/xfs/734 b/tests/xfs/734
> new file mode 100755
> index 00000000..847c5bfd
> --- /dev/null
> +++ b/tests/xfs/734
> @@ -0,0 +1,44 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2018, Oracle and/or its affiliates. All Rights Reserved.
> +#
> +# FS QA Test No. 734
> +#
> +# Ensure that xfsprogs crc32 works correctly via xfs_io crc32selftest command.
> +#
> +seq=`basename "$0"`
> +seqres="$RESULT_DIR/$seq"
> +echo "QA output created by $seq"
> +
> +here=`pwd`
> +tmp=/tmp/$$
> +status=1 # failure is the default!
> +trap "_cleanup; exit \$status" 0 1 2 3 15
> +
> +_cleanup()
> +{
> + cd /
> + rm -rf "$tmp".*
> +}
> +
> +# get standard environment, filters and checks
> +. ./common/rc
> +. ./common/filter
> +
> +# real QA test starts here
> +_supported_os Linux
> +_supported_fs xfs
> +_require_xfs_io_command "crc32selftest"
Looks like the new command was renamed to "crc32cselftest", I did the
same rename on commit then.
> +
> +rm -f "$seqres.full"
> +
> +filter_selftest() {
> + sed -e 's/bytes in [0-9]* usec/bytes in XXX usec/g'
> +}
> +
> +$XFS_IO_PROG -c 'crc32selftest' | filter_selftest
Same here.
Thanks,
Eryu
> +
> +echo "Silence is golden."
> +# success, all done
> +status=0
> +exit
> diff --git a/tests/xfs/734.out b/tests/xfs/734.out
> new file mode 100644
> index 00000000..f2a3fdc1
> --- /dev/null
> +++ b/tests/xfs/734.out
> @@ -0,0 +1,3 @@
> +QA output created by 734
> +crc32c: tests passed, 225944 bytes in XXX usec
> +Silence is golden.
> diff --git a/tests/xfs/group b/tests/xfs/group
> index 2cec0585..de66378f 100644
> --- a/tests/xfs/group
> +++ b/tests/xfs/group
> @@ -491,3 +491,4 @@
> 491 auto quick fuzz
> 492 auto quick fuzz
> 493 auto quick fuzz
> +734 auto quick
prev parent reply other threads:[~2018-11-04 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 18:12 [PATCH] xfs: test packaged crc32c code Darrick J. Wong
2018-11-03 15:38 ` Eryu Guan [this message]
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=20181103153803.GB12788@desktop \
--to=guaneryu@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.