From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
zlang@kernel.org, nirjhar.roy.lists@gmail.com
Subject: [PATCH v2] check: Fix fs specfic imports when $FSTYPE!=$OLD_FSTYPE
Date: Tue, 28 Jan 2025 05:00:22 +0000 [thread overview]
Message-ID: <3b980d028a8ae1496c13ebe3a6685fbc472c5bc0.1738040386.git.nirjhar.roy.lists@gmail.com> (raw)
Bug Description:
_test_mount function is failing with the following error:
./common/rc: line 4716: _xfs_prepare_for_eio_shutdown: command not found
check: failed to mount /dev/loop0 on /mnt1/test
when the second section in local.config file is xfs and the first section
is non-xfs.
It can be easily reproduced with the following local.config file
[s2]
export FSTYP=ext4
export TEST_DEV=/dev/loop0
export TEST_DIR=/mnt1/test
export SCRATCH_DEV=/dev/loop1
export SCRATCH_MNT=/mnt1/scratch
[s1]
export FSTYP=xfs
export TEST_DEV=/dev/loop0
export TEST_DIR=/mnt1/test
export SCRATCH_DEV=/dev/loop1
export SCRATCH_MNT=/mnt1/scratch
./check selftest/001
Root cause:
When _test_mount() is executed for the second section, the FSTYPE has
already changed but the new fs specific common/$FSTYP has not yet
been done. Hence _xfs_prepare_for_eio_shutdown() is not found and
the test run fails.
Fix:
Remove the additional _test_mount in check file just before ". commom/rc"
since ". commom/rc" is already sourcing fs specific imports and doing a
_test_mount.
Fixes: 1a49022fab9b4 ("fstests: always use fail-at-unmount semantics for XFS")
Signed-off-by: Nirjhar Roy (IBM) <nirjhar.roy.lists@gmail.com>
---
check | 12 +++---------
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/check b/check
index 607d2456..5cb4e7eb 100755
--- a/check
+++ b/check
@@ -784,15 +784,9 @@ function run_section()
status=1
exit
fi
- if ! _test_mount
- then
- echo "check: failed to mount $TEST_DEV on $TEST_DIR"
- status=1
- exit
- fi
- # TEST_DEV has been recreated, previous FSTYP derived from
- # TEST_DEV could be changed, source common/rc again with
- # correct FSTYP to get FSTYP specific configs, e.g. common/xfs
+ # Previous FSTYP derived from TEST_DEV could be changed, source
+ # common/rc again with correct FSTYP to get FSTYP specific configs,
+ # e.g. common/xfs
. common/rc
_prepare_test_list
elif [ "$OLD_TEST_FS_MOUNT_OPTS" != "$TEST_FS_MOUNT_OPTS" ]; then
--
2.34.1
next reply other threads:[~2025-01-28 5:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 5:00 Nirjhar Roy (IBM) [this message]
2025-01-28 18:09 ` [PATCH v2] check: Fix fs specfic imports when $FSTYPE!=$OLD_FSTYPE Darrick J. Wong
2025-01-29 11:18 ` Nirjhar Roy (IBM)
2025-01-29 16:02 ` Darrick J. Wong
2025-01-31 13:19 ` Nirjhar Roy (IBM)
2025-01-31 16:24 ` Darrick J. Wong
2025-02-01 6:35 ` Zorro Lang
2025-02-06 18:02 ` Nirjhar Roy (IBM)
2025-02-10 14:23 ` Zorro Lang
2025-02-21 4:14 ` Nirjhar Roy (IBM)
2025-02-21 5:47 ` Zorro Lang
2025-02-21 5:49 ` Nirjhar Roy (IBM)
2025-02-06 5:35 ` Nirjhar Roy (IBM)
2025-02-06 15:52 ` Darrick J. Wong
2025-02-06 17:58 ` Nirjhar Roy (IBM)
2025-02-01 7:05 ` 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=3b980d028a8ae1496c13ebe3a6685fbc472c5bc0.1738040386.git.nirjhar.roy.lists@gmail.com \
--to=nirjhar.roy.lists@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--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