From: Amir Goldstein <amir73il@gmail.com>
To: Zorro Lang <zlang@redhat.com>
Cc: "Miklos Szeredi" <miklos@szeredi.hu>,
"Christian Brauner" <brauner@kernel.org>,
"André Almeida" <andrealmeid@igalia.com>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH v2 3/6] generic/604: do not run with overlayfs
Date: Tue, 3 Jun 2025 12:07:42 +0200 [thread overview]
Message-ID: <20250603100745.2022891-4-amir73il@gmail.com> (raw)
In-Reply-To: <20250603100745.2022891-1-amir73il@gmail.com>
Overlayfs does not allow mounting over again with the same layers
until umount is fully completed, so is not appropriate for this test
which tries to mount in parallel to umount.
This is manifested as the test failure below when overlayfs strict mount
checks are enabled by enabling the index feature:
$ echo Y > /sys/module/overlay/parameters/index
...
+mount: /vdf/ovl-mnt: /vdf already mounted or mount point busy.
+ dmesg(1) may have more information after failed mount system call.
+mount /vdf /vdf/ovl-mnt failed
Opt-out of this test with overlayfs and remove the hacks that were placed
by commit 06cee932 ("generic/604: Fix for overlayfs") to make the test pass
with overlayfs in the first place.
Tested-by: André Almeida <andrealmeid@igalia.com>
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
tests/generic/604 | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/tests/generic/604 b/tests/generic/604
index 744d3456..481250fd 100755
--- a/tests/generic/604
+++ b/tests/generic/604
@@ -13,6 +13,9 @@ _begin_fstest auto quick mount
# Import common functions.
. ./common/filter
+# Overlayfs does not allow mounting over again with the same layers
+# until umount is fully completed, so is not appropriate for this test.
+_exclude_fs overlay
# Modify as appropriate.
_require_scratch
@@ -22,11 +25,9 @@ _scratch_mount
for i in $(seq 0 500); do
$XFS_IO_PROG -f -c "pwrite 0 4K" $SCRATCH_MNT/$i >/dev/null
done
-# For overlayfs, avoid unmounting the base fs after _scratch_mount tries to
-# mount the base fs. Delay the mount attempt by a small amount in the hope
-# that the mount() call will try to lock s_umount /after/ umount has already
-# taken it.
-_unmount $SCRATCH_MNT &
+# Delay the mount attempt by a small amount in the hope that the mount() call
+# will try to lock s_umount /after/ umount has already taken it.
+_scratch_unmount &
sleep 0.01s ; _scratch_mount
wait
--
2.34.1
next prev parent reply other threads:[~2025-06-03 10:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 10:07 [PATCH v2 0/6] fstests overlay fixes for v2025.05.25 Amir Goldstein
2025-06-03 10:07 ` [PATCH v2 1/6] overlay: workaround libmount failure to remount,ro Amir Goldstein
2025-06-05 17:51 ` Zorro Lang
2025-06-05 18:30 ` Amir Goldstein
2025-06-06 1:12 ` Zorro Lang
2025-06-06 7:35 ` Amir Goldstein
2025-06-06 10:35 ` Zorro Lang
2025-06-06 10:58 ` Amir Goldstein
2025-06-06 11:42 ` Zorro Lang
2025-06-06 14:23 ` André Almeida
2025-06-06 15:21 ` Amir Goldstein
2025-06-03 10:07 ` [PATCH v2 2/6] overlay: fix regression in _repair_overlay_scratch_fs Amir Goldstein
2025-06-05 17:47 ` Zorro Lang
2025-06-03 10:07 ` Amir Goldstein [this message]
2025-06-05 17:40 ` [PATCH v2 3/6] generic/604: do not run with overlayfs Zorro Lang
2025-06-03 10:07 ` [PATCH v2 4/6] generic/623: " Amir Goldstein
2025-06-05 17:32 ` Zorro Lang
2025-06-05 18:38 ` Amir Goldstein
2025-06-06 1:45 ` Zorro Lang
2025-06-06 7:23 ` Amir Goldstein
2025-06-06 10:29 ` Zorro Lang
2025-06-06 12:12 ` Amir Goldstein
2025-06-08 13:16 ` Zorro Lang
2025-06-09 11:01 ` Amir Goldstein
2025-06-09 11:12 ` Amir Goldstein
2025-06-09 17:26 ` Zorro Lang
2025-06-09 17:43 ` Amir Goldstein
2025-06-09 16:57 ` Zorro Lang
2025-06-03 10:07 ` [PATCH v2 5/6] generic: remove incorrect _require_idmapped_mounts checks Amir Goldstein
2025-06-05 17:24 ` Zorro Lang
2025-06-05 18:33 ` Amir Goldstein
2025-06-03 10:07 ` [PATCH v2 6/6] generic/699: fix failure with MOUNT_OPTIONS Amir Goldstein
2025-06-05 17:46 ` 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=20250603100745.2022891-4-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=brauner@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=zlang@redhat.com \
/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).