From: Eryu Guan <eguan@redhat.com>
To: xiao yang <yangx.jy@cn.fujitsu.com>
Cc: david@fromorbit.com, bfoster@redhat.com, fstests@vger.kernel.org,
darrick.wong@oracle.com
Subject: Re: [PATCH v4 2/3] common/filter: factor out expected XFS warnings for mount
Date: Thu, 18 Jan 2018 16:48:57 +0800 [thread overview]
Message-ID: <20180118084857.GU3102@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1516087617-2077-2-git-send-email-yangx.jy@cn.fujitsu.com>
On Tue, Jan 16, 2018 at 03:26:56PM +0800, xiao yang wrote:
> 1) Move filter_xfs_dmesg from xfs/098 to common/filter, and rename
> it as _filter_assert_dmesg.
>
> 2) Add _require_no_xfs_debug helper to skip xfs/098 if it is tested
> on debug build.
>
> Signed-off-by: xiao yang <yangx.jy@cn.fujitsu.com>
> ---
> common/filter | 9 +++++++++
> tests/xfs/098 | 18 ++++++------------
> 2 files changed, 15 insertions(+), 12 deletions(-)
>
> diff --git a/common/filter b/common/filter
> index 8e1fdb4..8f90b01 100644
> --- a/common/filter
> +++ b/common/filter
> @@ -570,5 +570,14 @@ _filter_aiodio_dmesg()
> -e "s#$warn9#Intentional warnings in dio_complete#"
> }
>
> +# We generate assert WARNINGs on CONFIG_XFS_WARN build as expected and make
> +# sure test doesn't fail because of these warnings. This is a helper for
> +# _check_dmesg() to filter out them.
> +_filter_assert_dmesg()
> +{
> + local warn="WARNING:.*fs/xfs/xfs_message\.c:.*asswarn.*"
When bug_on_assert=0, the "asswarn" can be "assfail" too, we should
filter out both cases.
> + sed -e "s#$warn#Intentional warnings in asswarn#"
> +}
> +
> # make sure this script returns success
> /bin/true
> diff --git a/tests/xfs/098 b/tests/xfs/098
> index 9bcd94b..f924b32 100755
> --- a/tests/xfs/098
> +++ b/tests/xfs/098
> @@ -47,6 +47,9 @@ _cleanup()
> _supported_fs xfs
> _supported_os Linux
>
> +# We corrupt XFS on purpose, and debug built XFS would crash due to
> +# assert failure, so skip if we're testing on a debug built XFS
> +_require_no_xfs_debug
Same here, _require_no_xfs_bug_on_assert if we all agree to do so.
Thanks,
Eryu
> _require_scratch
> test -n "${FORCE_FUZZ}" || _require_scratch_xfs_crc
> _require_attrs
> @@ -56,16 +59,6 @@ test -z "${FUZZ_ARGS}" && FUZZ_ARGS="-n 8 -3"
>
> rm -f $seqres.full
>
> -# If we corrupt log on a CONFIG_XFS_WARN build, there will be mount related
> -# WARNINGs in dmesg as expected. We don't want to simply _disable_dmesg_check
> -# which could miss other potential bugs, so filter out the intentional WARNINGs,
> -# make sure test doesn't fail because of this warning and fails on other WARNINGs.
> -filter_xfs_dmesg()
> -{
> - local warn="WARNING:.*fs/xfs/xfs_message\.c:.*asswarn.*"
> - sed -e "s#$warn#Intentional warnings in asswarn#"
> -}
> -
> TESTDIR="${SCRATCH_MNT}/scratchdir"
> TESTFILE="${TESTDIR}/testfile"
>
> @@ -107,8 +100,9 @@ _scratch_mount 2>/dev/null && _fail "mount should not succeed"
> echo "+ repair fs"
> _repair_scratch_fs >> $seqres.full 2>&1
>
> -# mount may trigger related WARNINGs, so filter them.
> -_check_dmesg filter_xfs_dmesg
> +# We may trigger mounted related WARNINGs if we corrupt log on a
> +# CONFIG_XFS_WARN build, so filter them.
> +_check_dmesg _filter_assert_dmesg
>
> echo "+ mount image (2)"
> _scratch_mount
> --
> 1.8.3.1
>
>
>
next prev parent reply other threads:[~2018-01-18 8:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 8:25 [PATCH] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-11 18:07 ` Darrick J. Wong
2018-01-12 1:58 ` Xiao Yang
2018-01-12 6:14 ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory xiao yang
2018-01-12 6:14 ` [PATCH v2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12 6:19 ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory Xiao Yang
2018-01-12 6:16 ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-12 6:16 ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12 7:49 ` Eryu Guan
2018-01-12 8:36 ` Dave Chinner
2018-01-12 8:50 ` Eryu Guan
2018-01-12 16:41 ` Darrick J. Wong
2018-01-13 2:23 ` Dave Chinner
2018-01-15 6:29 ` Eryu Guan
2018-01-15 7:48 ` [PATCH v3 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-15 7:48 ` [PATCH v3 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-15 7:48 ` [PATCH v3 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-15 12:45 ` [PATCH v2 2/2] " Brian Foster
2018-01-15 21:03 ` Dave Chinner
2018-01-16 4:02 ` Eryu Guan
2018-01-16 6:41 ` Xiao Yang
2018-01-16 7:26 ` [PATCH v4 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-16 7:26 ` [PATCH v4 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-18 8:48 ` Eryu Guan [this message]
2018-01-18 8:56 ` Xiao Yang
2018-01-16 7:26 ` [PATCH v4 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 8:46 ` Eryu Guan
2018-01-18 10:49 ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-18 10:49 ` [PATCH v5 2/3] common/filter: Factor out expected XFS warnings for assert xiao yang
2018-01-18 18:29 ` Darrick J. Wong
2018-01-19 2:51 ` Eryu Guan
2018-01-19 4:04 ` Xiao Yang
2018-01-19 5:38 ` [PATCH v6 2/3] common: Add _require_no_xfs_bug_on_assert && Factor out filter_xfs_dmesg xiao yang
2018-01-19 5:38 ` [PATCH v6 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 10:49 ` [PATCH v5 " xiao yang
2018-01-18 18:19 ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db Darrick J. Wong
2018-01-16 8:50 ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit Dave Chinner
2018-01-16 14:09 ` Brian Foster
2018-01-18 8:44 ` Eryu Guan
2018-01-16 13:58 ` Brian Foster
2018-01-12 7:44 ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db Eryu Guan
2018-01-12 16:43 ` Darrick J. Wong
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=20180118084857.GU3102@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--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