From: Amir Goldstein <amir73il@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: [GIT PULL] overlayfs fixes for 7.4-rc2
Date: Fri, 6 Nov 2026 07:46:59 +0100 [thread overview]
Message-ID: <20261106064659.3809691-1-amir73il@gmail.com> (raw)
Hi Linus,
Please pull overlayfs fixes for 7.4-rc2.
- Was in linux-next overnight
- Gone through the usual overlayfs test routines
- Merges cleanly with master branch of the moment
VFS NOTE: added export of symbol dentry_open_nonotify() that was added
by commit ebe559609d78 ("fs: get rid of __FMODE_NONOTIFY kludge").
Note that before removing the __FMODE_NONOTIFY kludge, overlayfs and other
modules could open a FMODE_NONOTIFY file with dentry_open().
Thanks,
Amir.
----------------------------------------------------------------
The following changes since commit 51628610f9187c1c1cfe499d92e066bc22ad9693:
vfs: fix take_dentry_name_snapshot() semantics (2026-11-03 08:28: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-rc2
for you to fetch changes up to db1c5da238dc80a61ab429a7b71b0e2835766c45:
selftests/fscontext_ns: expect EINVAL for overlay descendant userns create (2026-11-04 21:47:48 +0100)
----------------------------------------------------------------
overlayfs fixes for 7.4-rc2
- Fix a self deadlock of a fanotify permission event listener that also
watches the layers, when it reads an overlay directory
- Three casefold fixes, found by Chris Mason's AI review
- Fix a decode of a modified file handle with nfs_export=on, which could
read the stale lower data of a copied up file, also found by Chris
Mason's AI review
- Fix an overlay selftest after an errno change
----------------------------------------------------------------
Amir Goldstein (3):
ovl: inherit FMODE_NONOTIFY when opening directory realfiles
ovl: inherit FMODE_NONOTIFY when reading directory layers
selftests/fscontext_ns: expect EINVAL for overlay descendant userns create
Chris Mason (4):
ovl: fail the mount if the casefold flag has changed
ovl: do not let chattr change the casefold flag
ovl: fix whiteout creation in casefolded directories
ovl: look up the index by the decoded origin
Documentation/filesystems/overlayfs.rst | 3 +-
fs/open.c | 1 +
fs/overlayfs/dir.c | 46 ++++++++++++----------
fs/overlayfs/export.c | 4 +-
fs/overlayfs/inode.c | 8 ++++
fs/overlayfs/namei.c | 13 ++++--
fs/overlayfs/overlayfs.h | 21 +++++-----
fs/overlayfs/readdir.c | 35 +++++++++-------
fs/overlayfs/super.c | 12 +++++-
fs/overlayfs/util.c | 13 +++++-
.../filesystems/fscontext_ns/fscontext_ns_test.c | 2 +-
11 files changed, 102 insertions(+), 56 deletions(-)
next reply other threads:[~2026-11-06 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 6:46 Amir Goldstein [this message]
2026-11-06 17:43 ` 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=20261106064659.3809691-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.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 \
--cc=viro@zeniv.linux.org.uk \
/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®