From: Christoph Hellwig <hch@lst.de>
To: zlang@kernel.org
Cc: djwong@kernel.org, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH] xfs/216: pass -t xfs to _mount
Date: Thu, 7 May 2026 07:09:49 +0200 [thread overview]
Message-ID: <20260507050950.1300316-1-hch@lst.de> (raw)
Without this, mount probes different file system type, which ended up
exposing kernel bugs in blocksize > PAGE_SIZE bugs in tons of
legacy file systems. Bypass that by forcing XFS and making the
mount a little more efficient.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
tests/xfs/216 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/xfs/216 b/tests/xfs/216
index 091c11d08642..2096dd9b53d9 100755
--- a/tests/xfs/216
+++ b/tests/xfs/216
@@ -57,7 +57,7 @@ _do_mkfs()
echo -n "fssize=${i}g "
$MKFS_XFS_PROG -f -b size=4096 -l version=2 \
-d size=${i}g $loop_mkfs_opts $loop_dev |grep log
- _mount $loop_dev $LOOP_MNT
+ _mount -t xfs $loop_dev $LOOP_MNT
echo "test write" > $LOOP_MNT/test
_unmount $LOOP_MNT > /dev/null 2>&1
done
--
2.53.0
next reply other threads:[~2026-05-07 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 5:09 Christoph Hellwig [this message]
2026-05-07 9:20 ` [PATCH] xfs/216: pass -t xfs to _mount Andrey Albershteyn
2026-05-07 18:45 ` 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=20260507050950.1300316-1-hch@lst.de \
--to=hch@lst.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox