Linux Overlay Filesystem development
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Zorro Lang <zlang@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH] overlay/081: fix test when running with index enabled
Date: Sun, 17 Dec 2023 17:00:17 +0200	[thread overview]
Message-ID: <20231217150017.569077-1-amir73il@gmail.com> (raw)

Test overlay/081 fails with:
 CONFIG_OVERLAY_FS_INDEX=y
or
 echo Y > /sys/modules/overlay/params/index

The reason is that mount option uuid=off has the undesired side effect
of disabling index feature.

uuid=null is exactly the same as uuid=off for the purpose of this test
but without the undesired side effect.

The test was created to test the new modes uuid=null/auto/on, so the
fact that is is testing the mode uuid=off is just an oversight.

Covert the use of uuid=off to uuid=null to fix this problem.

Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---

Zorro,

Following your report that the new test overlay/084 is failing with
non-default overlayfs Kconfig [1], I reran the existing overlay tests
with non-default config.

The run with CONFIG_OVERLAY_FS_INDEX=y found another failure in a test
that was added recently to cover a new feature in v6.6.

Thanks,
Amir.


[1] https://lore.kernel.org/fstests/20231210204503.poggjg4z57eg2nn7@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com/

 tests/overlay/081 | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/tests/overlay/081 b/tests/overlay/081
index 05156a3c..481e9931 100755
--- a/tests/overlay/081
+++ b/tests/overlay/081
@@ -5,7 +5,7 @@
 # FSQA Test No. 081
 #
 # Test persistent (and optionally unique) overlayfs fsid
-# with mount options uuid=null/on introduced in kernel v6.6
+# with mount options uuid=null/auto/on introduced in kernel v6.6
 #
 . ./common/preamble
 _begin_fstest auto quick
@@ -55,7 +55,7 @@ _scratch_mount
 
 ovl_fsid=$(stat -f -c '%i' $test_dir)
 [[ "$ovl_fsid" == "$upper_fsid" ]] || \
-	echo "Overlayfs (uuid=auto) and upper fs fsid differ"
+	echo "Overlayfs (after uuid=null) and upper fs fsid differ"
 
 $UMOUNT_PROG $SCRATCH_MNT
 
@@ -74,16 +74,16 @@ _scratch_mount
 
 ovl_fsid=$(stat -f -c '%i' $test_dir)
 [[ "$ovl_fsid" == "$ovl_unique_fsid" ]] || \
-	echo "Overlayfs (uuid=auto) unique fsid is not persistent"
+	echo "Overlayfs (after uuid=on) unique fsid is not persistent"
 
 $UMOUNT_PROG $SCRATCH_MNT
 
 # Test ignore existing persistent fsid on explicit opt-out
-_scratch_mount -o uuid=off
+_scratch_mount -o uuid=null
 
 ovl_fsid=$(stat -f -c '%i' $test_dir)
 [[ "$ovl_fsid" == "$upper_fsid" ]] || \
-	echo "Overlayfs (uuid=off) and upper fs fsid differ"
+	echo "Overlayfs (uuid=null) and upper fs fsid differ"
 
 $UMOUNT_PROG $SCRATCH_MNT
 
@@ -92,7 +92,7 @@ _overlay_scratch_mount_dirs "$upperdir:$lowerdir" "-" "-" -o ro,uuid=on
 
 ovl_fsid=$(stat -f -c '%i' $test_dir)
 [[ "$ovl_fsid" == "$lower_fsid" ]] || \
-	echo "Overlayfs (uuid=null) and lower fs fsid differ"
+	echo "Overlayfs (no upper) and lower fs fsid differ"
 
 # Re-create fresh overlay layers, so following (uuid=auto) mounts
 # will behave as first time mount of a new overlayfs
@@ -110,7 +110,7 @@ _scratch_mount
 ovl_fsid=$(stat -f -c '%i' $test_dir)
 ovl_unique_fsid=$ovl_fsid
 [[ "$ovl_fsid" != "$upper_fsid" ]] || \
-	echo "Overlayfs (uuid=auto) and upper fs fsid are the same"
+	echo "Overlayfs (new) and upper fs fsid are the same"
 
 $UMOUNT_PROG $SCRATCH_MNT
 
-- 
2.34.1


             reply	other threads:[~2023-12-17 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 15:00 Amir Goldstein [this message]
2023-12-23 18:56 ` [PATCH] overlay/081: fix test when running with index enabled 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=20231217150017.569077-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --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