All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/6] fstests overlay fixes for v2025.05.25
Date: Tue,  3 Jun 2025 12:07:39 +0200	[thread overview]
Message-ID: <20250603100745.2022891-1-amir73il@gmail.com> (raw)

Zorro,

My first batch of fixes [1] was addressing overlayfs test failures after
upgrade of test machine to a newer distro (trixie) with libmount v1.41.

After a closer look, I found some tests that regressed into _notrun,
which is harder to notice at first glance.

Tests generic/{633,697,697} were regressed in v2025.03.17.
Test generic/699 always had a problem AFAICT, but I only just tested
it with custom MOUNT_OPTIONS.

Lastly, following the review discussion between Miklos and Karel Zak,
I changed the workaround to the regressions observed after upgrade to
newer libmount.

Thanks,
Amir.

Changes since v1 [1]:
- Change workaround from LIBMOUNT_FORCE_MOUNT2 to --options-mode=ignore
- Add two commits to fix tests that were not running by mistake

[1] https://lore.kernel.org/fstests/20250526143500.1520660-1-amir73il@gmail.com/

Amir Goldstein (6):
  overlay: workaround libmount failure to remount,ro
  overlay: fix regression in _repair_overlay_scratch_fs
  generic/604: do not run with overlayfs
  generic/623: do not run with overlayfs
  generic: remove incorrect _require_idmapped_mounts checks
  generic/699: fix failure with MOUNT_OPTIONS

 common/overlay    |  7 ++++++-
 common/rc         | 10 +++++++++-
 tests/generic/330 |  2 +-
 tests/generic/604 | 11 ++++++-----
 tests/generic/623 |  1 +
 tests/generic/633 |  1 -
 tests/generic/696 |  1 -
 tests/generic/697 |  1 -
 tests/generic/699 | 17 ++++++++++-------
 tests/overlay/035 |  2 +-
 10 files changed, 34 insertions(+), 19 deletions(-)

-- 
2.34.1


             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 Amir Goldstein [this message]
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 ` [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-1-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 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.