From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH 4/5] ext4/054: skip test if the dax mount option is enabled
Date: Fri, 24 Jun 2022 23:07:17 -0400 [thread overview]
Message-ID: <20220625030718.1215980-5-tytso@mit.edu> (raw)
In-Reply-To: <20220625030718.1215980-1-tytso@mit.edu>
The ext4/054 test explicitly creates a file system with a 1k
blocksize. This can't possibly work on if the dax mount option is
enabled, so change ext4/054 to use _scratch_mkfs_blocksized, and and a
check to _scratch_mkfs_blocksized to _notrun the test if the block
size is less than the page size.
Also remove an unnecessary _require_test declaration since this test
does not use the test device.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
common/rc | 3 +++
tests/ext4/054 | 5 ++---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/common/rc b/common/rc
index 9378ff26..3014f5fc 100644
--- a/common/rc
+++ b/common/rc
@@ -1220,6 +1220,9 @@ _scratch_mkfs_blocksized()
if ! [[ $blocksize =~ $re ]] ; then
_notrun "error: _scratch_mkfs_sized: block size \"$blocksize\" not an integer."
fi
+ if [ $blocksize -lt $(get_page_size) ]; then
+ _exclude_scratch_mount_option dax
+ fi
case $FSTYP in
btrfs)
diff --git a/tests/ext4/054 b/tests/ext4/054
index 9a11719f..e23acbb1 100755
--- a/tests/ext4/054
+++ b/tests/ext4/054
@@ -19,7 +19,6 @@ _begin_fstest auto quick dangerous_fuzzers
# real QA test starts here
_supported_fs ext4
-_require_test
_require_scratch_nocheck
_require_xfs_io_command "falloc"
_require_xfs_io_command "pwrite"
@@ -28,8 +27,8 @@ _require_xfs_io_command "fpunch"
_require_command "$DEBUGFS_PROG" debugfs
# In order to accurately construct the damaged extent in the following
-# test steps, the blocksize is set to 1024 here
-_scratch_mkfs "-b 1024" > $seqres.full 2>&1
+# test steps, the block size is set to 1024 here
+_scratch_mkfs_blocksized 1024 >> $seqres.full 2>&1
_scratch_mount
TEST_FILE="${SCRATCH_MNT}/testfile"
--
2.31.0
next prev parent reply other threads:[~2022-06-25 3:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 3:07 [PATCH 0/5] Misceillaneous ext4 test fix ups Theodore Ts'o
2022-06-25 3:07 ` [PATCH 1/5] ext4/050: support indirect as well as extent mapped journals Theodore Ts'o
2022-06-28 4:24 ` Zorro Lang
2022-06-25 3:07 ` [PATCH 2/5] ext4/044: skip test if the file system does not have a journal Theodore Ts'o
2022-06-28 4:28 ` Zorro Lang
2022-06-28 4:32 ` Zorro Lang
2022-06-28 18:20 ` Theodore Ts'o
2022-06-25 3:07 ` [PATCH 3/5] ext4/045: clean up unnecessary arguments to _require_e2fsprogs Theodore Ts'o
2022-06-28 4:37 ` Zorro Lang
2022-06-28 18:21 ` Theodore Ts'o
2022-06-25 3:07 ` Theodore Ts'o [this message]
2022-06-28 4:39 ` [PATCH 4/5] ext4/054: skip test if the dax mount option is enabled Zorro Lang
2022-06-25 3:07 ` [PATCH 5/5] ext4/055: skip test if dax mount option is used Theodore Ts'o
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=20220625030718.1215980-5-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=fstests@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.