From: Catherine Hoang <catherine.hoang@oracle.com>
To: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Cc: djwong@kernel.org, john.g.garry@oracle.com
Subject: [PATCH 5/6] common/atomicwrites: fix _require_scratch_write_atomic
Date: Tue, 13 May 2025 17:29:14 -0700 [thread overview]
Message-ID: <20250514002915.13794-6-catherine.hoang@oracle.com> (raw)
In-Reply-To: <20250514002915.13794-1-catherine.hoang@oracle.com>
From: "Darrick J. Wong" <djwong@kernel.org>
Fix this function to call _notrun whenever something fails. If we can't
figure out the atomic write geometry, then we haven't satisfied the
preconditions for the test.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
Signed-off-by: Catherine Hoang <catherine.hoang@oracle.com>
---
common/atomicwrites | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/common/atomicwrites b/common/atomicwrites
index 9ec1ca68..391bb6f6 100644
--- a/common/atomicwrites
+++ b/common/atomicwrites
@@ -28,21 +28,23 @@ _require_scratch_write_atomic()
{
_require_scratch
- awu_min_bdev=$(_get_atomic_write_unit_min $SCRATCH_DEV)
- awu_max_bdev=$(_get_atomic_write_unit_max $SCRATCH_DEV)
+ local awu_min_bdev=$(_get_atomic_write_unit_min $SCRATCH_DEV)
+ local awu_max_bdev=$(_get_atomic_write_unit_max $SCRATCH_DEV)
if [ $awu_min_bdev -eq 0 ] && [ $awu_max_bdev -eq 0 ]; then
_notrun "write atomic not supported by this block device"
fi
- _scratch_mkfs > /dev/null 2>&1
- _scratch_mount
+ _scratch_mkfs > /dev/null 2>&1 || \
+ _notrun "cannot format scratch device for atomic write checks"
+ _try_scratch_mount || \
+ _notrun "cannot mount scratch device for atomic write checks"
- testfile=$SCRATCH_MNT/testfile
+ local testfile=$SCRATCH_MNT/testfile
touch $testfile
- awu_min_fs=$(_get_atomic_write_unit_min $testfile)
- awu_max_fs=$(_get_atomic_write_unit_max $testfile)
+ local awu_min_fs=$(_get_atomic_write_unit_min $testfile)
+ local awu_max_fs=$(_get_atomic_write_unit_max $testfile)
_scratch_unmount
--
2.34.1
next prev parent reply other threads:[~2025-05-14 0:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 0:29 [PATCH 0/6] atomic writes tests Catherine Hoang
2025-05-14 0:29 ` [PATCH 1/6] generic/765: fix a few issues Catherine Hoang
2025-05-14 12:47 ` John Garry
2025-05-14 15:38 ` Darrick J. Wong
2025-05-14 23:42 ` Catherine Hoang
2025-05-15 1:47 ` Darrick J. Wong
2025-05-15 8:16 ` John Garry
2025-05-15 14:54 ` Darrick J. Wong
2025-05-15 17:57 ` John Garry
2025-05-15 21:50 ` Catherine Hoang
2025-05-16 6:59 ` John Garry
2025-05-17 3:17 ` Ritesh Harjani
2025-05-14 0:29 ` [PATCH 2/6] generic/765: adjust various things Catherine Hoang
2025-05-14 12:59 ` John Garry
2025-05-17 3:36 ` Ritesh Harjani
2025-05-14 0:29 ` [PATCH 3/6] generic/765: move common atomic write code to a library file Catherine Hoang
2025-05-14 13:00 ` John Garry
2025-05-17 3:49 ` Ritesh Harjani
2025-05-14 0:29 ` [PATCH 4/6] common/atomicwrites: adjust a few more things Catherine Hoang
2025-05-14 13:11 ` John Garry
2025-05-14 15:40 ` Darrick J. Wong
2025-05-17 3:59 ` Ritesh Harjani
2025-05-14 0:29 ` Catherine Hoang [this message]
2025-05-14 13:14 ` [PATCH 5/6] common/atomicwrites: fix _require_scratch_write_atomic John Garry
2025-05-14 0:29 ` [PATCH 6/6] generic: various atomic write tests with scsi_debug Catherine Hoang
2025-05-14 13:41 ` John Garry
2025-05-14 16:01 ` Darrick J. Wong
2025-05-14 16:30 ` John Garry
2025-05-14 23:49 ` Catherine Hoang
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=20250514002915.13794-6-catherine.hoang@oracle.com \
--to=catherine.hoang@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).