From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH 2/2] xfs/21[67]: fix mkfs log concurrency detection
Date: Wed, 20 May 2026 12:01:12 -0700 [thread overview]
Message-ID: <20260520190112.GE9544@frogsfrogsfrogs> (raw)
In-Reply-To: <20260520185202.GD9544@frogsfrogsfrogs>
From: Darrick J. Wong <djwong@kernel.org>
Both of these tests use _scratch_mkfs_xfs_supports_concurrency to detect
if they should be adding -lconcurrency=0 to the mkfs options that are
used to format a loop device.
However, this doesn't work in practice because of three factors: 1) the
scratch device could have an external log set up; 2) the loop device
does /not/ have an external log device; and 3) -lconcurrency isn't
compatible with -llogdev.
Fix this by creating a more general mkfs option detection helper and use
that once we have the loop device set up.
Cc: <fstests@vger.kernel.org> # v2026.05.17
Fixes: ffc8bad17e5b2f ("xfs/21{6,7} Use default -l concurrency=0 on mkfs.xfs that supports it")
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
common/xfs | 15 +++++++++++++++
tests/xfs/216 | 9 ++++-----
tests/xfs/217 | 9 ++++-----
3 files changed, 23 insertions(+), 10 deletions(-)
diff --git a/common/xfs b/common/xfs
index 88299acdd086be..232d40fd5e01b1 100644
--- a/common/xfs
+++ b/common/xfs
@@ -64,6 +64,21 @@ _scratch_mkfs_xfs_opts()
echo "$MKFS_XFS_PROG $SCRATCH_OPTIONS $mkfs_opts"
}
+_mkfs_xfs_supported()
+{
+ local mkfs_opts=$*
+
+ $MKFS_XFS_PROG -f -N $MKFS_OPTIONS $mkfs_opts
+ local mkfs_status=$?
+
+ # a mkfs failure may be caused by conflicts between $MKFS_OPTIONS and
+ # $mkfs_opts, try again without $MKFS_OPTIONS
+ if [ $mkfs_status -ne 0 -a -n "$mkfs_opts" ]; then
+ $MKFS_XFS_PROG -f -N $mkfs_opts
+ mkfs_status=$?
+ fi
+ return $mkfs_status
+}
_scratch_mkfs_xfs_supported()
{
diff --git a/tests/xfs/216 b/tests/xfs/216
index e3be9f3fe39ee0..bd98ee4dbfe960 100755
--- a/tests/xfs/216
+++ b/tests/xfs/216
@@ -22,11 +22,6 @@ _cleanup()
_require_scratch
_scratch_mkfs_xfs >/dev/null 2>&1
-if _scratch_mkfs_xfs_supports_concurrency -l >> $seqres.full 2>&1; then
- loop_mkfs_opts="-l concurrency=0"
-else
- loop_mkfs_opts=""
-fi
_scratch_mount
_require_loop
@@ -76,6 +71,10 @@ mkdir $LOOP_MNT
loop_dev=$(_create_loop_device $LOOP_IMG)
+if _mkfs_xfs_supported $loop_mkfs_opts -l concurrency=0 $loop_dev &>> $seqres.full; then
+ loop_mkfs_opts="$loop_mkfs_opts -l concurrency=0"
+fi
+
# walk over standard sizes (up to 256GB)
_do_mkfs 1 2 4 8 16 32 64 128 256
diff --git a/tests/xfs/217 b/tests/xfs/217
index 5b210627b5ed18..5ba0b2198eb84f 100755
--- a/tests/xfs/217
+++ b/tests/xfs/217
@@ -21,11 +21,6 @@ _cleanup()
_require_scratch
_scratch_mkfs_xfs >/dev/null 2>&1
-if _scratch_mkfs_xfs_supports_concurrency -l >> $seqres.full 2>&1; then
- loop_mkfs_opts="-l concurrency=0 -d concurrency=0"
-else
- loop_mkfs_opts=""
-fi
_scratch_mount
# 16T mkfs requires a bit over 2G free
_require_fs_space $SCRATCH_MNT 2202000
@@ -63,6 +58,10 @@ fi
loop_dev=$(_create_loop_device $LOOP_IMG)
+if _mkfs_xfs_supported $loop_mkfs_opts -l concurrency=0 -d concurrency=0 $loop_dev &>> $seqres.full; then
+ loop_mkfs_opts="$loop_mkfs_opts -l concurrency=0 -d concurrency=0"
+fi
+
#
# walk over "new" sizes supported by recent xfsprogs.
# Note that the last test is for 16TB-1GB as 32bit platforms only support
next prev parent reply other threads:[~2026-05-20 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 18:52 [PATCH 1/2] common/xfs: fix _scratch_mkfs_xfs_supports_concurrency Darrick J. Wong
2026-05-20 19:01 ` Darrick J. Wong [this message]
2026-05-25 5:46 ` [PATCH 2/2] xfs/21[67]: fix mkfs log concurrency detection Christoph Hellwig
2026-05-29 4:21 ` Darrick J. Wong
2026-05-29 5:45 ` Christoph Hellwig
2026-05-29 9:43 ` Zorro Lang
2026-05-25 5:43 ` [PATCH 1/2] common/xfs: fix _scratch_mkfs_xfs_supports_concurrency Christoph Hellwig
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=20260520190112.GE9544@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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 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.