From: Amir Goldstein <amir73il@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Giuseppe Scrivano <giuseppe@scrivano.org>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: [GIT PULL] overlayfs fixes for 7.4-rc3
Date: Sat, 14 Nov 2026 11:28:46 +0100 [thread overview]
Message-ID: <20261114102846.574470-1-amir73il@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=true, Size: 2939 bytes --]
Hi Linus,
Please pull overlayfs fixes for 7.4-rc3.
- Was in linux-next overnight
- Gone through the usual overlayfs test routines
- Merges cleanly with master branch of the moment
Thanks,
Amir.
----------------------------------------------------------------
The following changes since commit 7475ea8b58616b33c04afb976cf0fbaad9dd63fb:
Linux 7.4-rc2 (2026-11-08 16:22:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs.git ovl-fixes-7.4-rc3
for you to fetch changes up to 748739f3171ed1c44a30a98b0e0341b1a8d62d31:
selftests: overlayfs: reject different lower idmaps on same fs (2026-11-12 13:38:59 +0100)
----------------------------------------------------------------
overlayfs fixes for 7.4-rc3
- Fixes for data-only layers (composefs), some for regressions from
v6.16, which relaxed the requirements for redirects to data-only layers
- Fix a use-after-free in lookup of a hardlink with a FUSE upper,
reported by Sashiko
- Fix a mount failure right after unmount of an overlay with the same
upperdir
- Reject lower layers on the same fs with different idmaps, which could
decode file handles through the wrong layer
- Minor fixes for a memory leak, an error message and readdir d_ino
----------------------------------------------------------------
Amir Goldstein (5):
ovl: do not read the flags of a put upper dentry in lookup
ovl: fix leak of lowerdata redirect on ovl_get_inode() failure
ovl: do not check the deferred lowerdata redirect on index lookup
ovl: do not allow nfs_export with data-only layers
ovl: report the requested redirect_dir mode in conflicting options
Daejun Park (1):
ovl: bump the impure dir version when linking a file with origin
Denis V. Lunev (1):
ovl: release the upperdir/workdir in-use locks before the umount sync
Giuseppe Scrivano (3):
ovl: do not always clear absolute_redirect
ovl: follow lower to lowerdata redirects from any lower layer
ovl: return EIO if the lowerdata is missing
Jérémy Jean (2):
ovl: reject different lower idmaps on the same fs
selftests: overlayfs: reject different lower idmaps on same fs
Documentation/filesystems/overlayfs.rst | 24 +++---
fs/overlayfs/dir.c | 20 ++---
fs/overlayfs/namei.c | 61 ++++++++++++---
fs/overlayfs/overlayfs.h | 22 +++++-
fs/overlayfs/ovl_entry.h | 2 +
fs/overlayfs/params.c | 91 +++++++++++++++++-----
fs/overlayfs/params.h | 2 +
fs/overlayfs/super.c | 52 +++++++++++--
fs/overlayfs/util.c | 12 +++
.../filesystems/overlayfs/idmapped_mounts.c | 45 +++++++++++
10 files changed, 270 insertions(+), 61 deletions(-)
reply other threads:[~2026-11-14 10:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261114102846.574470-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=giuseppe@scrivano.org \
--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®