From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@kernel.org>
Cc: Anand Jain <anand.jain@oracle.com>,
Filipe Manana <fdmanana@suse.com>,
"Darrick J. Wong" <djwong@kernel.org>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: [PATCH 05/12] generic/590: split XFS RT specific bits out
Date: Wed, 10 Dec 2025 06:46:51 +0100 [thread overview]
Message-ID: <20251210054831.3469261-6-hch@lst.de> (raw)
In-Reply-To: <20251210054831.3469261-1-hch@lst.de>
Currently generic/590 runs a very different test on XFS that creates
a lot device and so on. Split that out into a new XFS-specific test,
and let generic/590 always run using the file system parameter specified
in the config even for XFS.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
tests/generic/590 | 68 ++-------------------------
tests/xfs/650 | 117 ++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/650.out | 2 +
3 files changed, 123 insertions(+), 64 deletions(-)
create mode 100755 tests/xfs/650
create mode 100644 tests/xfs/650.out
diff --git a/tests/generic/590 b/tests/generic/590
index ba1337a856f1..54c26f2ae5ed 100755
--- a/tests/generic/590
+++ b/tests/generic/590
@@ -4,27 +4,15 @@
#
# FS QA Test 590
#
-# Test commit 0c4da70c83d4 ("xfs: fix realtime file data space leak") and
-# 69ffe5960df1 ("xfs: don't check for AG deadlock for realtime files in
-# bunmapi"). On XFS without the fixes, truncate will hang forever. On other
-# filesystems, this just tests writing into big fallocates.
+# Tests writing into big fallocates.
+#
+# Based on an XFS RT subvolume specific test now split into xfs/650.
#
. ./common/preamble
_begin_fstest auto prealloc preallocrw
-# Override the default cleanup function.
-_cleanup()
-{
- _scratch_unmount &>/dev/null
- [ -n "$loop_dev" ] && _destroy_loop_device $loop_dev
- cd /
- rm -f $tmp.*
- rm -f "$TEST_DIR/$seq"
-}
-
. ./common/filter
-_require_scratch_nocheck
_require_xfs_io_command "falloc"
maxextlen=$((0x1fffff))
@@ -32,54 +20,7 @@ bs=4096
rextsize=4
filesz=$(((maxextlen + 1) * bs))
-must_disable_feature() {
- local feat="$1"
-
- # If mkfs doesn't know about the feature, we don't need to disable it
- $MKFS_XFS_PROG --help 2>&1 | grep -q "${feat}=0" || return 1
-
- # If turning the feature on works, we don't need to disable it
- _scratch_mkfs_xfs_supported -m "${feat}=1" "${disabled_features[@]}" \
- > /dev/null 2>&1 && return 1
-
- # Otherwise mkfs knows of the feature and formatting with it failed,
- # so we do need to mask it.
- return 0
-}
-
-extra_options=""
-# If we're testing XFS, set up the realtime device to reproduce the bug.
-if [[ $FSTYP = xfs ]]; then
- # If we don't have a realtime device, set up a loop device on the test
- # filesystem.
- if [[ $USE_EXTERNAL != yes || -z $SCRATCH_RTDEV ]]; then
- _require_test
- loopsz="$((filesz + (1 << 26)))"
- _require_fs_space "$TEST_DIR" $((loopsz / 1024))
- $XFS_IO_PROG -c "truncate $loopsz" -f "$TEST_DIR/$seq"
- loop_dev="$(_create_loop_device "$TEST_DIR/$seq")"
- USE_EXTERNAL=yes
- SCRATCH_RTDEV="$loop_dev"
- disabled_features=()
-
- # disable reflink if not supported by realtime devices
- must_disable_feature reflink &&
- disabled_features=(-m reflink=0)
-
- # disable rmap if not supported by realtime devices
- must_disable_feature rmapbt &&
- disabled_features+=(-m rmapbt=0)
- fi
- extra_options="$extra_options -r extsize=$((bs * rextsize))"
- extra_options="$extra_options -d agsize=$(((maxextlen + 1) * bs / 2)),rtinherit=1"
-
- _scratch_mkfs $extra_options "${disabled_features[@]}" >>$seqres.full 2>&1
- _try_scratch_mount >>$seqres.full 2>&1 || \
- _notrun "mount failed, kernel doesn't support realtime?"
- _scratch_unmount
-else
- _scratch_mkfs $extra_options >>$seqres.full 2>&1
-fi
+_scratch_mkfs >>$seqres.full 2>&1
_scratch_mount
_require_fs_space "$SCRATCH_MNT" $((filesz / 1024))
@@ -112,7 +53,6 @@ $XFS_IO_PROG -c "pwrite -b 1M -W 0 $(((maxextlen + 2 - rextsize) * bs))" \
# Truncate the extents.
$XFS_IO_PROG -c "truncate 0" -c fsync "$SCRATCH_MNT/file"
-# We need to do this before the loop device gets torn down.
_scratch_unmount
_check_scratch_fs
diff --git a/tests/xfs/650 b/tests/xfs/650
new file mode 100755
index 000000000000..d8f70539665f
--- /dev/null
+++ b/tests/xfs/650
@@ -0,0 +1,117 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (c) 2019 Facebook. All Rights Reserved.
+#
+# FS QA Test 650
+#
+# Test commit 0c4da70c83d4 ("xfs: fix realtime file data space leak") and
+# 69ffe5960df1 ("xfs: don't check for AG deadlock for realtime files in
+# bunmapi"). On XFS without the fixes, truncate will hang forever.
+#
+. ./common/preamble
+_begin_fstest auto prealloc preallocrw
+
+# Override the default cleanup function.
+_cleanup()
+{
+ _scratch_unmount &>/dev/null
+ [ -n "$loop_dev" ] && _destroy_loop_device $loop_dev
+ cd /
+ rm -f $tmp.*
+ rm -f "$TEST_DIR/$seq"
+}
+
+. ./common/filter
+
+_require_scratch_nocheck
+_require_xfs_io_command "falloc"
+
+maxextlen=$((0x1fffff))
+bs=4096
+rextsize=4
+filesz=$(((maxextlen + 1) * bs))
+
+must_disable_feature() {
+ local feat="$1"
+
+ # If mkfs doesn't know about the feature, we don't need to disable it
+ $MKFS_XFS_PROG --help 2>&1 | grep -q "${feat}=0" || return 1
+
+ # If turning the feature on works, we don't need to disable it
+ _scratch_mkfs_xfs_supported -m "${feat}=1" "${disabled_features[@]}" \
+ > /dev/null 2>&1 && return 1
+
+ # Otherwise mkfs knows of the feature and formatting with it failed,
+ # so we do need to mask it.
+ return 0
+}
+
+extra_options=""
+# Set up the realtime device to reproduce the bug.
+
+# If we don't have a realtime device, set up a loop device on the test
+# filesystem.
+if [[ $USE_EXTERNAL != yes || -z $SCRATCH_RTDEV ]]; then
+ _require_test
+ loopsz="$((filesz + (1 << 26)))"
+ _require_fs_space "$TEST_DIR" $((loopsz / 1024))
+ $XFS_IO_PROG -c "truncate $loopsz" -f "$TEST_DIR/$seq"
+ loop_dev="$(_create_loop_device "$TEST_DIR/$seq")"
+ USE_EXTERNAL=yes
+ SCRATCH_RTDEV="$loop_dev"
+ disabled_features=()
+
+ # disable reflink if not supported by realtime devices
+ must_disable_feature reflink &&
+ disabled_features=(-m reflink=0)
+
+ # disable rmap if not supported by realtime devices
+ must_disable_feature rmapbt &&
+ disabled_features+=(-m rmapbt=0)
+fi
+extra_options="$extra_options -r extsize=$((bs * rextsize))"
+extra_options="$extra_options -d agsize=$(((maxextlen + 1) * bs / 2)),rtinherit=1"
+
+_scratch_mkfs $extra_options "${disabled_features[@]}" >>$seqres.full 2>&1
+_try_scratch_mount >>$seqres.full 2>&1 || \
+ _notrun "mount failed, kernel doesn't support realtime?"
+_scratch_unmount
+_scratch_mount
+_require_fs_space "$SCRATCH_MNT" $((filesz / 1024))
+
+# Allocate maxextlen + 1 blocks. As long as the allocator does something sane,
+# we should end up with two extents that look something like:
+#
+# u3.bmx[0-1] = [startoff,startblock,blockcount,extentflag]
+# 0:[0,0,2097148,1]
+# 1:[2097148,2097148,4,1]
+#
+# Extent 0 has blockcount = ALIGN_DOWN(maxextlen, rextsize). Extent 1 is
+# adjacent and has blockcount = rextsize. Both are unwritten.
+$XFS_IO_PROG -c "falloc 0 $filesz" -c fsync -f "$SCRATCH_MNT/file"
+
+# Write extent 0 + one block of extent 1. Our extents should end up like so:
+#
+# u3.bmx[0-1] = [startoff,startblock,blockcount,extentflag]
+# 0:[0,0,2097149,0]
+# 1:[2097149,2097149,3,1]
+#
+# Extent 0 is written and has blockcount = ALIGN_DOWN(maxextlen, rextsize) + 1,
+# Extent 1 is adjacent, unwritten, and has blockcount = rextsize - 1 and
+# startblock % rextsize = 1.
+#
+# The -b is just to speed things up (doing GBs of I/O in 4k chunks kind of
+# sucks).
+$XFS_IO_PROG -c "pwrite -b 1M -W 0 $(((maxextlen + 2 - rextsize) * bs))" \
+ "$SCRATCH_MNT/file" >> "$seqres.full"
+
+# Truncate the extents.
+$XFS_IO_PROG -c "truncate 0" -c fsync "$SCRATCH_MNT/file"
+
+# We need to do this before the loop device gets torn down.
+_scratch_unmount
+_check_scratch_fs
+
+echo "Silence is golden"
+status=0
+exit
diff --git a/tests/xfs/650.out b/tests/xfs/650.out
new file mode 100644
index 000000000000..d7a3e4b63483
--- /dev/null
+++ b/tests/xfs/650.out
@@ -0,0 +1,2 @@
+QA output created by 650
+Silence is golden
--
2.47.3
next prev parent reply other threads:[~2025-12-10 5:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 5:46 stop overriding SCRATCH_{,LOG,RT}DEV Christoph Hellwig
2025-12-10 5:46 ` [PATCH 01/12] dmflakey: override SCRATCH_DEV in _init_flakey Christoph Hellwig
2025-12-10 5:46 ` [PATCH 02/12] ext4/006: call e2fsck directly Christoph Hellwig
2025-12-10 19:32 ` Darrick J. Wong
2025-12-11 4:52 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 03/12] common: add a _check_dev_fs helper Christoph Hellwig
2025-12-10 23:24 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 04/12] ext4/032: use _check_dev_fs Christoph Hellwig
2025-12-10 23:24 ` Darrick J. Wong
2025-12-10 5:46 ` Christoph Hellwig [this message]
2025-12-10 22:51 ` [PATCH 05/12] generic/590: split XFS RT specific bits out Darrick J. Wong
2025-12-10 5:46 ` [PATCH 06/12] xfs/157: don't override SCRATCH_{,LOG,RT}DEV Christoph Hellwig
2025-12-10 20:05 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 07/12] xfs/185: don't use SCRATCH_{,RT}DEV helpers Christoph Hellwig
2025-12-10 20:02 ` Darrick J. Wong
2025-12-11 5:00 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 08/12] xfs/424: don't use SCRATCH_DEV helpers Christoph Hellwig
2025-12-10 19:55 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 09/12] xfs/521: require a real SCRATCH_RTDEV Christoph Hellwig
2025-12-10 19:54 ` Darrick J. Wong
2025-12-11 4:58 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 10/12] xfs/528: " Christoph Hellwig
2025-12-10 19:52 ` Darrick J. Wong
2025-12-11 4:57 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 11/12] xfs/530: " Christoph Hellwig
2025-12-10 19:49 ` Darrick J. Wong
2025-12-11 4:55 ` Christoph Hellwig
2025-12-12 20:00 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 12/12] xfs/650: " Christoph Hellwig
2025-12-10 19:45 ` Darrick J. Wong
2025-12-10 22:50 ` Darrick J. Wong
2025-12-11 4:54 ` 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=20251210054831.3469261-6-hch@lst.de \
--to=hch@lst.de \
--cc=anand.jain@oracle.com \
--cc=djwong@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox