All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@igalia.com>
To: Amir Goldstein <amir73il@gmail.com>, Zorro Lang <zlang@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Christian Brauner <brauner@kernel.org>,
	linux-unionfs@vger.kernel.org, fstests@vger.kernel.org,
	Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH v2 1/6] overlay: workaround libmount failure to remount,ro
Date: Fri, 6 Jun 2025 16:23:27 +0200	[thread overview]
Message-ID: <bdd067c5-6115-4190-9e64-019607e9cc30@igalia.com> (raw)
In-Reply-To: <CAOQ4uxh9b285dnw+SO2h6HqtNC5Xog0TQSqhFAQaV1brBnVxVQ@mail.gmail.com>

Hi Amir,

On 6/6/25 09:35, Amir Goldstein wrote:
> On Fri, Jun 6, 2025 at 3:12 AM Zorro Lang <zlang@redhat.com> wrote:
>> On Thu, Jun 05, 2025 at 08:30:53PM +0200, Amir Goldstein wrote:
>>> On Thu, Jun 5, 2025 at 7:51 PM Zorro Lang <zlang@redhat.com> wrote:
>>>> On Tue, Jun 03, 2025 at 12:07:40PM +0200, Amir Goldstein wrote:
>>>>> libmount >= v1.39 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.
>>>>>
>>>>> We workaround this problem with --options-mode ignore.
>>>>>
>>>>> Reported-by: André Almeida <andrealmeid@igalia.com>
>>>>> Suggested-by: Karel Zak <kzak@redhat.com>
>>>>> Link: https://lore.kernel.org/linux-fsdevel/20250521-ovl_ro-v1-1-2350b1493d94@igalia.com/
>>>>> Link: https://lore.kernel.org/fstests/CAJfpegtJ3SDKmC80B4AfWiC3JmtWdW2+78fRZVtsuhe-wSRPvg@mail.gmail.com/
>>>>> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
>>>>> ---
>>>>>
>>>>> Changes since v1 [1]:
>>>>> - Change workaround from LIBMOUNT_FORCE_MOUNT2 to --options-mode=ignore
>>>>>
>>>>> [1] https://lore.kernel.org/fstests/20250526143500.1520660-1-amir73il@gmail.com/
>>>> I'm not sure if I understand clearly. Does overlay list are fixing this issue
>>>> on kernel side, then providing a workaround to fstests to avoid the issue be
>>>> triggered too?
>>>>
>>> Noone agreed to fix it on the kernel side.
>>> At least not yet.
>> If so, I have two questions:)
>> 1) Will overlay fix it on kernel or mount util side?
> This is not known at this time.

Do you know how calling fsconfig() in a "redundant" way behaves in other 
filesystems? Do they allow to call fsconfig() calls that doesn't change 
the state, like a noop?


  parent reply	other threads:[~2025-06-06 14:23 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 [this message]
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 ` [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=bdd067c5-6115-4190-9e64-019607e9cc30@igalia.com \
    --to=andrealmeid@igalia.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.