From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@kernel.org>,
"Christian Brauner (Amutable)" <brauner@kernel.org>
Subject: [PATCH 1/2] dcache: don't leave negative dentries in casefolded directories
Date: Fri, 23 Oct 2026 14:44:22 +0200 [thread overview]
Message-ID: <20261023-work-dcache-casefold-v1-1-1b0bd5c73a69@kernel.org> (raw)
In-Reply-To: <20261023-work-dcache-casefold-v1-0-1b0bd5c73a69@kernel.org>
ext4, f2fs and tmpfs keep negative dentries out of casefolded
directories. A negative dentry remembers one spelling of the name and
the next create() through it would write that spelling to disk.
So their ->lookup() doesn't cache a miss and their ->unlink() and
->rmdir() call d_invalidate() on the dentry so that d_delete() doesn't
turn it into a negative dentry.
But d_invalidate() is the wrong primitive for that. It's for a name that
went stale. It walks the subtree, prunes it and detaches every mount it
finds, under namespace_sem, and here that runs from inside the
filesystem's own directory operation. ext4_rmdir() does it with the
journal handle still open and ext4_unlink() does it even when the
unlink failed. All anyone wanted is the unhash.
So d_delete() now unhashes the dentry when the parent is casefolded,
next to the dentry-negative sysctl that does the same for every
directory. ext4, f2fs and tmpfs drop their d_invalidate() calls.
Nothing changes for a casefolded directory. A miss still isn't cached
and a removed name still doesn't leave a negative dentry behind. The
target of a rename over an existing name, which tmpfs also passes
through shmem_unlink(), doesn't turn negative either. vfs_rename()
detaches its mounts and d_move() unhashes it. A failed unlink or rmdir
now leaves the dentry hashed and its mounts in place, as in any other
directory.
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
---
fs/dcache.c | 8 +++++++-
fs/ext4/namei.c | 18 ------------------
fs/f2fs/namei.c | 9 ---------
mm/shmem.c | 7 -------
4 files changed, 7 insertions(+), 35 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
index efd9332c8407..f5cbb2e24e53 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -2746,6 +2746,12 @@ struct dentry *d_hash_and_lookup(struct dentry *dir, struct qstr *name)
return d_lookup(dir, name);
}
+static __always_inline bool d_delete_drop(struct dentry *dentry)
+{
+ return dentry_negative_policy ||
+ IS_CASEFOLDED(d_inode(dentry->d_parent));
+}
+
/*
* When a file is deleted, we have two options:
* - turn this dentry into a negative dentry
@@ -2777,7 +2783,7 @@ void d_delete(struct dentry * dentry)
* Are we the only user?
*/
if (dentry->d_lockref.count == 1) {
- if (dentry_negative_policy)
+ if (d_delete_drop(dentry))
__d_drop(dentry);
dentry->d_flags &= ~DCACHE_CANT_MOUNT;
dentry_unlink_inode(dentry);
diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
index 6e0630a49e48..c4b1121471e6 100644
--- a/fs/ext4/namei.c
+++ b/fs/ext4/namei.c
@@ -3209,15 +3209,6 @@ static int ext4_rmdir(struct inode *dir, struct dentry *dentry)
ext4_fc_track_unlink(handle, dentry);
retval = ext4_mark_inode_dirty(handle, dir);
- /* VFS negative dentries are incompatible with Encoding and
- * Case-insensitiveness. Eventually we'll want avoid
- * invalidating the dentries here, alongside with returning the
- * negative dentries at ext4_lookup(), when it is better
- * supported by the VFS for the CI case.
- */
- if (IS_ENABLED(CONFIG_UNICODE) && IS_CASEFOLDED(dir))
- d_invalidate(dentry);
-
end_rmdir:
brelse(bh);
if (handle)
@@ -3320,15 +3311,6 @@ static int ext4_unlink(struct inode *dir, struct dentry *dentry)
retval = __ext4_unlink(dir, &dentry->d_name, d_inode(dentry), dentry);
- /* VFS negative dentries are incompatible with Encoding and
- * Case-insensitiveness. Eventually we'll want avoid
- * invalidating the dentries here, alongside with returning the
- * negative dentries at ext4_lookup(), when it is better
- * supported by the VFS for the CI case.
- */
- if (IS_ENABLED(CONFIG_UNICODE) && IS_CASEFOLDED(dir))
- d_invalidate(dentry);
-
out_trace:
trace_ext4_unlink_exit(dentry, retval);
return retval;
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
index 233c07fec171..30f6b8448eee 100644
--- a/fs/f2fs/namei.c
+++ b/fs/f2fs/namei.c
@@ -631,15 +631,6 @@ static int f2fs_unlink(struct inode *dir, struct dentry *dentry)
if (err)
goto out;
- /* VFS negative dentries are incompatible with Encoding and
- * Case-insensitiveness. Eventually we'll want avoid
- * invalidating the dentries here, alongside with returning the
- * negative dentries at f2fs_lookup(), when it is better
- * supported by the VFS for the CI case.
- */
- if (IS_ENABLED(CONFIG_UNICODE) && IS_CASEFOLDED(dir))
- d_invalidate(dentry);
-
if (IS_DIRSYNC(dir))
err = f2fs_sync_fs(F2FS_I_SB(dir)->sb, 1);
out:
diff --git a/mm/shmem.c b/mm/shmem.c
index 0d891ade18b5..5a353ac32573 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3953,13 +3953,6 @@ static int shmem_unlink(struct inode *dir, struct dentry *dentry)
inode_inc_iversion(dir);
simple_unlink(dir, dentry);
- /*
- * For now, VFS can't deal with case-insensitive negative dentries, so
- * we invalidate them
- */
- if (IS_ENABLED(CONFIG_UNICODE) && IS_CASEFOLDED(dir))
- d_invalidate(dentry);
-
return 0;
}
--
2.53.0
next prev parent reply other threads:[~2026-10-23 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 12:44 [PATCH 0/2] dcache: don't leave negative dentries in casefolded directories Christian Brauner
2026-10-23 12:44 ` Christian Brauner [this message]
2026-10-24 19:20 ` [PATCH 1/2] " Eric Biggers
2026-10-23 12:44 ` [PATCH 2/2] xfs: unhash a removed name in ascii-ci mode instead of invalidating it Christian Brauner
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=20261023-work-dcache-casefold-v1-1-1b0bd5c73a69@kernel.org \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=krisman@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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