From: Chao Yu <chao@kernel.org>
To: fstests@vger.kernel.org
Cc: guan@eryu.me, linux-f2fs-devel@lists.sourceforge.net, zlang@kernel.org
Subject: Re: [PATCH] generic: adjust strict SPO recovery testcases for f2fs
Date: Wed, 1 Jun 2022 00:04:41 +0800 [thread overview]
Message-ID: <1643075e-f830-5e0a-9c12-e32a37ca0f5d@kernel.org> (raw)
In-Reply-To: <20220521031621.3494402-1-chao@kernel.org>
+Cc Zorro,
Any comments?
On 2022/5/21 11:16, Chao Yu wrote:
> Testcases like generic 342/502/526/527 expect that filesystems will
> recover all related metadata changes to the file which was fsynced
> before sudden power off.
>
> This patch adjusts to use "fsync_mode=strict" mountoption for f2fs
> to pass these testcases.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> tests/generic/342 | 5 +++++
> tests/generic/502 | 5 +++++
> tests/generic/526 | 5 +++++
> tests/generic/527 | 5 +++++
> 4 files changed, 20 insertions(+)
>
> diff --git a/tests/generic/342 b/tests/generic/342
> index 676b876b..cdffaaf3 100755
> --- a/tests/generic/342
> +++ b/tests/generic/342
> @@ -31,6 +31,11 @@ _require_dm_target flakey
>
> _scratch_mkfs >>$seqres.full 2>&1
> _require_metadata_journaling $SCRATCH_DEV
> +
> +if [ $FSTYP = "f2fs" ]; then
> + export MOUNT_OPTIONS="-o fsync_mode=strict $MOUNT_OPTIONS"
> +fi
> +
> _init_flakey
> _mount_flakey
>
> diff --git a/tests/generic/502 b/tests/generic/502
> index b0f9077f..b5589b81 100755
> --- a/tests/generic/502
> +++ b/tests/generic/502
> @@ -34,6 +34,11 @@ _require_dm_target flakey
>
> _scratch_mkfs >>$seqres.full 2>&1
> _require_metadata_journaling $SCRATCH_DEV
> +
> +if [ $FSTYP = "f2fs" ]; then
> + export MOUNT_OPTIONS="-o fsync_mode=strict $MOUNT_OPTIONS"
> +fi
> +
> _init_flakey
> _mount_flakey
>
> diff --git a/tests/generic/526 b/tests/generic/526
> index dc7cb36c..ada4dbee 100755
> --- a/tests/generic/526
> +++ b/tests/generic/526
> @@ -32,6 +32,11 @@ _require_dm_target flakey
>
> _scratch_mkfs >>$seqres.full 2>&1
> _require_metadata_journaling $SCRATCH_DEV
> +
> +if [ $FSTYP = "f2fs" ]; then
> + export MOUNT_OPTIONS="-o fsync_mode=strict $MOUNT_OPTIONS"
> +fi
> +
> _init_flakey
> _mount_flakey
>
> diff --git a/tests/generic/527 b/tests/generic/527
> index 40cd1c6a..de09d171 100755
> --- a/tests/generic/527
> +++ b/tests/generic/527
> @@ -32,6 +32,11 @@ _require_dm_target flakey
>
> _scratch_mkfs >>$seqres.full 2>&1
> _require_metadata_journaling $SCRATCH_DEV
> +
> +if [ $FSTYP = "f2fs" ]; then
> + export MOUNT_OPTIONS="-o fsync_mode=strict $MOUNT_OPTIONS"
> +fi
> +
> _init_flakey
> _mount_flakey
>
next prev parent reply other threads:[~2022-05-31 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 3:16 [PATCH] generic: adjust strict SPO recovery testcases for f2fs Chao Yu
2022-05-31 16:04 ` Chao Yu [this message]
2022-05-31 19:33 ` Zorro Lang
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=1643075e-f830-5e0a-9c12-e32a37ca0f5d@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@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