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 6/6] generic/699: fix failure with MOUNT_OPTIONS
Date: Tue, 3 Jun 2025 12:07:45 +0200 [thread overview]
Message-ID: <20250603100745.2022891-7-amir73il@gmail.com> (raw)
In-Reply-To: <20250603100745.2022891-1-amir73il@gmail.com>
generic/699 uses overalyfs helper _overlay_mount_dirs, which is meant to
be used by overlayfs tests, where MOUNT_OPTIONS refer to overalyfs mount
options.
Using this helper from a generic test when FSTYP is not overlay is
causing undesired results. For example, when MOUNT_OPTIONS is defined
and includes a mount option not supported by overalyfs (e.g. 'acl'),
the test is notrun because of:
mount: /vdc/ovl-merge: fsconfig() failed: overlay: Unknown parameter 'acl'.
There is no other generic test that includes the common/overlay helpers
and uses them, so remove this practice from generic/699 as well.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
tests/generic/699 | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/tests/generic/699 b/tests/generic/699
index 620a40aa..2a6f857d 100755
--- a/tests/generic/699
+++ b/tests/generic/699
@@ -8,7 +8,6 @@
# mounts specifically.
#
. ./common/preamble
-. ./common/overlay
_begin_fstest auto quick perms attr idmapped mount
# Override the default cleanup function.
@@ -96,20 +95,24 @@ reset_ownership()
stat -c '%u:%g' $path
}
+setup_overlayfs()
+{
+ mkdir -p $upper $work $merge
+ _mount -t overlay -o lowerdir=$lower,upperdir=$upper,workdir=$work \
+ overlay $merge $*
+}
+
# Prepare overlayfs with metacopy turned off.
setup_overlayfs_idmapped_lower_metacopy_off()
{
- mkdir -p $upper $work $merge
- _overlay_mount_dirs $lower $upper $work \
- overlay $merge -ometacopy=off || \
- _notrun "overlayfs doesn't support idmappped layers"
+ setup_overlayfs -ometacopy=off || \
+ _notrun "overlayfs doesn't support idmappped layers"
}
# Prepare overlayfs with metacopy turned on.
setup_overlayfs_idmapped_lower_metacopy_on()
{
- mkdir -p $upper $work $merge
- _overlay_mount_dirs $lower $upper $work overlay $merge -ometacopy=on
+ setup_overlayfs -ometacopy=on
}
reset_overlayfs()
--
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 ` [PATCH v2 3/6] generic/604: do not run with overlayfs Amir Goldstein
2025-06-05 17:40 ` 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 ` Amir Goldstein [this message]
2025-06-05 17:46 ` [PATCH v2 6/6] generic/699: fix failure with MOUNT_OPTIONS 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-7-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).