From: Christoph Hellwig <hch@lst.de>
To: zlang@kernel.org
Cc: djwong@kernel.org, fstests@vger.kernel.org
Subject: [PATCH] xfs/541: _notrun if the file system can't mount
Date: Tue, 28 Jan 2025 08:14:48 +0100 [thread overview]
Message-ID: <20250128071449.676462-1-hch@lst.de> (raw)
A file system created without an RT section might not be able to mount
with an rtdev specified if the RT device has a larger LBA size.
Instead of letting the test fail, _notrun it for that case.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
tests/xfs/541 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/xfs/541 b/tests/xfs/541
index 42bcd95802c5..c8b312fddc92 100755
--- a/tests/xfs/541
+++ b/tests/xfs/541
@@ -26,7 +26,7 @@ _require_scratch
# Format scratch fs with no realtime section.
SCRATCH_RTDEV="" _scratch_mkfs | _filter_mkfs 2> $tmp.mkfs >> $seqres.full
-_scratch_mount
+_try_scratch_mount || _notrun "Can't mount file system"
# Zoned file systems don't support rtextsize > 1
_require_xfs_scratch_non_zoned
--
2.45.2
next reply other threads:[~2025-01-28 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:14 Christoph Hellwig [this message]
2025-01-28 19:25 ` [PATCH] xfs/541: _notrun if the file system can't mount Darrick J. Wong
2025-01-29 5:49 ` Christoph Hellwig
2025-01-29 21:06 ` Darrick J. Wong
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=20250128071449.676462-1-hch@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=fstests@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