From: Eryu Guan <eguan@redhat.com>
To: Hou Tao <houtao1@huawei.com>
Cc: fstests@vger.kernel.org, guaneryu@gmail.com,
linux-xfs@vger.kernel.org, darrick.wong@oracle.com,
cmaiolino@redhat.com
Subject: Re: [PATCH v3 2/4] dmflakey: support error_writes feature for dm-flakey
Date: Thu, 9 Nov 2017 16:57:05 +0800 [thread overview]
Message-ID: <20171109085705.GW17339@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20171109073252.36001-3-houtao1@huawei.com>
On Thu, Nov 09, 2017 at 03:32:50PM +0800, Hou Tao wrote:
> Add _require_flakey_with_error_writes() to check the availability of
> dm-flakey target and its error_writes feature, and support for enabling
> FLAKEY_TABLE_ERROR table by passing FLAKEY_ERROR_WRITES to
> _load_flakey_table().
>
> Signed-off-by: Hou Tao <houtao1@huawei.com>
> ---
> common/dmflakey | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/common/dmflakey b/common/dmflakey
> index 16b82d2..845b466 100644
> --- a/common/dmflakey
> +++ b/common/dmflakey
> @@ -20,18 +20,43 @@
>
> FLAKEY_ALLOW_WRITES=0
> FLAKEY_DROP_WRITES=1
> +FLAKEY_ERROR_WRITES=2
>
> echo $MOUNT_OPTIONS | grep -q dax
> if [ $? -eq 0 ]; then
> _notrun "Cannot run tests with DAX on dmflakey devices"
> fi
>
> +_require_flakey_with_error_writes()
> +{
> + local SIZE
> + local TABLE
> + local NAME=flakey-test
> +
> + _require_dm_target flakey
> +
> + SIZE=`blockdev --getsz $SCRATCH_DEV`
> + TABLE="0 $SIZE flakey $SCRATCH_DEV 0 0 180 1 error_writes"
> +
> + $DMSETUP_PROG create $NAME --table "$TABLE" >/dev/null 2>&1
> + if [ $? -ne 0 ]; then
> + _notrun "This test requires error_writes feature in dm-flakey"
> + fi
> + $DMSETUP_PROG mknodes >/dev/null 2>&1
> +
> + # copy from _cleanup_flakey()
> + $UDEV_SETTLE_PROG >/dev/null 2>&1
> + $DMSETUP_PROG remove $NAME >/dev/null 2>&1
> + $DMSETUP_PROG mknodes >/dev/null 2>&1
How about just call _cleanup_flakey() here?
Thanks,
Eryu
> +}
> +
> _init_flakey()
> {
> local BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV`
> FLAKEY_DEV=/dev/mapper/flakey-test
> FLAKEY_TABLE="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 180 0"
> FLAKEY_TABLE_DROP="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 0 180 1 drop_writes"
> + FLAKEY_TABLE_ERROR="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 0 180 1 error_writes"
> $DMSETUP_PROG create flakey-test --table "$FLAKEY_TABLE" || \
> _fatal "failed to create flakey device"
> $DMSETUP_PROG mknodes > /dev/null 2>&1
> @@ -67,9 +92,9 @@ _cleanup_flakey()
> # table, so it simulates power failure.
> _load_flakey_table()
> {
> -
> table="$FLAKEY_TABLE"
> [ $1 -eq $FLAKEY_DROP_WRITES ] && table="$FLAKEY_TABLE_DROP"
> + [ $1 -eq $FLAKEY_ERROR_WRITES ] && table="$FLAKEY_TABLE_ERROR"
>
> suspend_opt="--nolockfs"
> [ $# -gt 1 ] && [ $2 -eq 1 ] && suspend_opt=""
> --
> 2.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-09 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 7:32 [PATCH v3 0/4] test for XFS umount hang caused by the pending dquota log item in AIL Hou Tao
2017-11-09 7:32 ` [PATCH v3 1/4] dmflakey: support multiple dm targets for a dm-flakey device Hou Tao
2017-11-09 8:56 ` Eryu Guan
2017-11-09 7:32 ` [PATCH v3 2/4] dmflakey: support error_writes feature for dm-flakey Hou Tao
2017-11-09 8:57 ` Eryu Guan [this message]
2017-11-09 7:32 ` [PATCH v3 3/4] xfs: test for umount hang caused by the pending dquota log item in AIL Hou Tao
2017-11-09 9:05 ` Eryu Guan
2017-12-05 0:47 ` Darrick J. Wong
2018-01-10 0:20 ` Darrick J. Wong
2017-11-09 7:32 ` [PATCH v3 4/4] common/rc: factor out _scratch_xfs_[get|set]_sb_field Hou Tao
2017-11-09 17:02 ` Darrick J. Wong
2017-11-09 8:54 ` [PATCH v3 0/4] test for XFS umount hang caused by the pending dquota log item in AIL Eryu Guan
2017-11-21 16:35 ` Carlos Maiolino
2017-11-20 15:13 ` Carlos Maiolino
2017-11-21 15:49 ` Carlos Maiolino
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=20171109085705.GW17339@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=houtao1@huawei.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).