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,
"André Almeida" <andrealmeid@igalia.com>,
"Karel Zak" <kzak@redhat.com>
Subject: [PATCH 1/4] overlay: workaround libmount failure to remount,ro
Date: Mon, 26 May 2025 16:34:56 +0200 [thread overview]
Message-ID: <20250526143500.1520660-2-amir73il@gmail.com> (raw)
In-Reply-To: <20250526143500.1520660-1-amir73il@gmail.com>
libmount v1.41 calls several unneeded fsconfig() calls to reconfigure
lowerdir/upperdir when user requests only -o remount,ro.
Those calls fail because overlayfs does not allow making any config
changes with new mount api, besides MS_RDONLY.
force mount(8) to use mount(2) to remount ro/rw to workaround
this issue, by setting LIBMOUNT_FORCE_MOUNT2=always.
Reported-by: André Almeida <andrealmeid@igalia.com>
Cc: Karel Zak <kzak@redhat.com>
Link: https://lore.kernel.org/linux-fsdevel/20250521-ovl_ro-v1-1-2350b1493d94@igalia.com/
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
common/overlay | 4 +++-
tests/overlay/035 | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/common/overlay b/common/overlay
index 01b6622f..2e36fa3d 100644
--- a/common/overlay
+++ b/common/overlay
@@ -127,7 +127,9 @@ _overlay_base_scratch_mount()
_overlay_scratch_mount()
{
if echo "$*" | grep -q remount; then
- $MOUNT_PROG $SCRATCH_MNT $*
+ # force mount(8) to use mount(2), to workaround libmount v1.41
+ # failed fsconfig() calls to reconfigure lowerdir/upperdir
+ LIBMOUNT_FORCE_MOUNT2=always $MOUNT_PROG $SCRATCH_MNT $*
return
fi
diff --git a/tests/overlay/035 b/tests/overlay/035
index 0b3257c4..2a4df99a 100755
--- a/tests/overlay/035
+++ b/tests/overlay/035
@@ -42,7 +42,7 @@ mkdir -p $lowerdir1 $lowerdir2 $upperdir $workdir
# Verify that overlay is mounted read-only and that it cannot be remounted rw.
_overlay_scratch_mount_opts -o"lowerdir=$lowerdir2:$lowerdir1"
touch $SCRATCH_MNT/foo 2>&1 | _filter_scratch
-$MOUNT_PROG -o remount,rw $SCRATCH_MNT 2>&1 | _filter_ro_mount
+_scratch_remount rw 2>&1 | _filter_ro_mount
$UMOUNT_PROG $SCRATCH_MNT
# Make workdir immutable to prevent workdir re-create on mount
--
2.34.1
next prev parent reply other threads:[~2025-05-26 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 14:34 [PATCH 0/4] fstests overlay fixes for v2025.05.25 Amir Goldstein
2025-05-26 14:34 ` Amir Goldstein [this message]
2025-05-27 14:48 ` [PATCH 1/4] overlay: workaround libmount failure to remount,ro Miklos Szeredi
2025-05-28 6:54 ` Amir Goldstein
2025-05-28 8:47 ` Karel Zak
2025-05-28 9:56 ` Miklos Szeredi
2025-05-28 10:54 ` Karel Zak
2025-05-28 11:47 ` Miklos Szeredi
2025-05-28 13:13 ` Karel Zak
2025-05-28 13:27 ` Miklos Szeredi
2025-05-28 10:58 ` Amir Goldstein
2025-05-26 14:34 ` [PATCH 2/4] overlay: fix regression in _repair_overlay_scratch_fs Amir Goldstein
2025-05-26 14:34 ` [PATCH 3/4] generic/604: do not run with overlayfs Amir Goldstein
2025-05-26 14:34 ` [PATCH 3/4] generic/604: opt-out " Amir Goldstein
2025-05-26 14:35 ` [PATCH 4/4] generic/623: do not run " Amir Goldstein
2025-05-26 17:05 ` [PATCH 0/4] fstests overlay fixes for v2025.05.25 André Almeida
2025-05-27 9:11 ` Amir Goldstein
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=20250526143500.1520660-2-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=fstests@vger.kernel.org \
--cc=kzak@redhat.com \
--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).