mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Christian Brauner <brauner@kernel.org>,
	Chenglong Tang <chenglongtang@google.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-unionfs@vger.kernel.org
Subject: [GIT PULL] overlayfs fixes for 7.0-rc6
Date: Sun, 29 Mar 2026 11:26:58 +0200	[thread overview]
Message-ID: <20260329092658.90712-1-amir73il@gmail.com> (raw)

Hi Linus,

Please pull overlayfs fixes for 7.0-rc6 to fix two regressions
from v6.7 (minor impact) and from v6.12 (major performance impact).

This branch has been sitting in linux-next for a couple of day and
it has gone through the usual overlayfs test routines.

The branch merges cleanly with master branch of the moment.

Thanks,
Amir.

----------------------------------------------------------------
The following changes since commit f338e77383789c0cae23ca3d48adcc5e9e137e3c:

  Linux 7.0-rc4 (2026-03-15 13:52:05 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs.git ovl-fixes-7.0-rc6

for you to fetch changes up to 1f6ee9be92f8df85a8c9a5a78c20fd39c0c21a95:

  ovl: make fsync after metadata copy-up opt-in mount option (2026-03-27 12:48:10 +0100)

----------------------------------------------------------------
overlayfs fixes for 7.0-rc6:

- Fix regression in 'xino' feature detection.
  I clumsily introduced this regression myself when working on another
  subsystem (fsnotify).  Both the regression and the fix have almost
  no visible impact on users except for some kmsg prints.

- Fix to performance regression in v6.12.
  This regression was reported by Google GOC developers.
  It is not uncommon these days for the year-old mature LTS to
  get adopted by distros and get exposed to many new workloads.
  We made a sub-smart move of making a behavior change in v6.12
  which could impact performance, without making it opt-in.
  Fixing this mistake retroactively, to be picked by LTS.

----------------------------------------------------------------
Amir Goldstein (1):
      ovl: fix wrong detection of 32bit inode numbers

Fei Lv (1):
      ovl: make fsync after metadata copy-up opt-in mount option

 Documentation/filesystems/overlayfs.rst | 50 +++++++++++++++++++++++++++++++++
 fs/overlayfs/copy_up.c                  |  6 ++--
 fs/overlayfs/overlayfs.h                | 21 ++++++++++++++
 fs/overlayfs/ovl_entry.h                |  7 +----
 fs/overlayfs/params.c                   | 33 ++++++++++++++++++----
 fs/overlayfs/super.c                    |  2 +-
 fs/overlayfs/util.c                     |  5 +++-
 7 files changed, 108 insertions(+), 16 deletions(-)

             reply	other threads:[~2026-03-29  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29  9:26 Amir Goldstein [this message]
2026-03-29  9:30 ` Amir Goldstein
2026-03-29 16:42 ` pr-tracker-bot

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=20260329092658.90712-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=chenglongtang@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®