From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 19/20] kill DCACHE_MAY_FREE
Date: Fri, 24 Nov 2023 06:06:43 +0000 [thread overview]
Message-ID: <20231124060644.576611-19-viro@zeniv.linux.org.uk> (raw)
In-Reply-To: <20231124060644.576611-1-viro@zeniv.linux.org.uk>
With the new ordering in __dentry_kill() it has become redundant -
it's set if and only if both DCACHE_DENTRY_KILLED and DCACHE_SHRINK_LIST
are set.
We set it in __dentry_kill(), after having set DCACHE_DENTRY_KILLED
with the only condition being that DCACHE_SHRINK_LIST is there;
all of that is done without dropping ->d_lock and the only place
that checks that flag (shrink_dentry_list()) does so under ->d_lock,
after having found the victim on its shrink list. Since DCACHE_SHRINK_LIST
is set only when placing dentry into shrink list and removed only by
shrink_dentry_list() itself, a check for DCACHE_DENTRY_KILLED in
there would be equivalent to check for DCACHE_MAY_FREE.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
fs/dcache.c | 6 ++----
include/linux/dcache.h | 1 -
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
index 26080f094508..64d8c1d36acb 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -614,10 +614,8 @@ static struct dentry *__dentry_kill(struct dentry *dentry)
}
spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
dentry_unlist(dentry);
- if (dentry->d_flags & DCACHE_SHRINK_LIST) {
- dentry->d_flags |= DCACHE_MAY_FREE;
+ if (dentry->d_flags & DCACHE_SHRINK_LIST)
can_free = false;
- }
spin_unlock(&dentry->d_lock);
if (likely(can_free))
dentry_free(dentry);
@@ -1072,7 +1070,7 @@ void shrink_dentry_list(struct list_head *list)
bool can_free;
rcu_read_unlock();
d_shrink_del(dentry);
- can_free = dentry->d_flags & DCACHE_MAY_FREE;
+ can_free = dentry->d_flags & DCACHE_DENTRY_KILLED;
spin_unlock(&dentry->d_lock);
if (can_free)
dentry_free(dentry);
diff --git a/include/linux/dcache.h b/include/linux/dcache.h
index b4449a1a47ff..48b393545ec2 100644
--- a/include/linux/dcache.h
+++ b/include/linux/dcache.h
@@ -202,7 +202,6 @@ struct dentry_operations {
#define DCACHE_SPECIAL_TYPE (5 << 20) /* Other file type */
#define DCACHE_SYMLINK_TYPE (6 << 20) /* Symlink */
-#define DCACHE_MAY_FREE BIT(23)
#define DCACHE_NOKEY_NAME BIT(25) /* Encrypted name encoded without key */
#define DCACHE_OP_REAL BIT(26)
--
2.39.2
next prev parent reply other threads:[~2023-11-24 6:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 6:05 [PATCHES] assorted dcache stuff Al Viro
2023-11-24 6:06 ` [PATCH 01/20] selinux: saner handling of policy reloads Al Viro
2023-11-24 6:06 ` [PATCH 02/20] ovl: stop using d_alloc_anon()/d_instantiate_anon() Al Viro
2023-11-24 6:06 ` [PATCH 03/20] struct dentry: get rid of randomize_layout idiocy Al Viro
2023-11-24 6:06 ` [PATCH 04/20] get rid of __dget() Al Viro
2023-11-24 6:06 ` [PATCH 05/20] DCACHE_... ->d_flags bits: switch to BIT() Al Viro
2023-11-24 6:06 ` [PATCH 06/20] DCACHE_COOKIE: RIP Al Viro
2023-11-24 6:06 ` [PATCH 07/20] kill d_{is,set}_fallthru() Al Viro
2023-11-24 6:06 ` [PATCH 08/20] dentry.h: trim externs Al Viro
2023-11-24 6:06 ` [PATCH 09/20] [software coproarchaeology] dentry.h: kill a mysterious comment Al Viro
2023-11-24 7:37 ` Amir Goldstein
2023-11-24 8:11 ` Al Viro
2023-11-24 8:26 ` Al Viro
2023-11-24 8:29 ` Christian Brauner
2023-11-24 6:06 ` [PATCH 10/20] kill d_backing_dentry() Al Viro
2023-11-24 6:06 ` [PATCH 11/20] kill d_instantate_anon(), fold __d_instantiate_anon() into remaining caller Al Viro
2023-11-24 6:06 ` [PATCH 12/20] d_alloc_pseudo(): move setting ->d_op there from the (sole) caller Al Viro
2023-11-24 6:06 ` [PATCH 13/20] nsfs: use d_make_root() Al Viro
2023-11-24 6:06 ` [PATCH 14/20] simple_fill_super(): don't bother with d_genocide() on failure Al Viro
2023-11-24 6:06 ` [PATCH 15/20] d_genocide(): move the extern into fs/internal.h Al Viro
2023-11-24 6:35 ` d_genocide()? What about d_holodomor(), d_massmurder(), d_execute_warcrimes()? " Cedric Blancher
2023-11-24 6:57 ` Al Viro
2023-11-24 7:48 ` Al Viro
2023-11-24 9:36 ` Martin Steigerwald
2023-11-24 18:21 ` identifiers Al Viro
2025-12-09 22:29 ` d_genocide()? What about d_holodomor(), d_massmurder(), d_execute_warcrimes()? Re: [PATCH 15/20] d_genocide(): move the extern into fs/internal.h Askar Safin
2023-11-24 6:06 ` [PATCH 16/20] get rid of DCACHE_GENOCIDE Al Viro
2023-11-24 6:06 ` [PATCH 17/20] d_alloc_parallel(): in-lookup hash insertion doesn't need an RCU variant Al Viro
2023-11-24 6:06 ` [PATCH 18/20] __d_unalias() doesn't use inode argument Al Viro
2023-11-24 6:06 ` Al Viro [this message]
2023-11-24 6:06 ` [PATCH 20/20] dcache: remove unnecessary NULL check in dget_dlock() Al Viro
2023-11-24 21:41 ` [PATCHES] assorted dcache stuff Linus Torvalds
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=20231124060644.576611-19-viro@zeniv.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®