From: Jeff Layton <jlayton@kernel.org>
To: corbet@lwn.net
Cc: viro@zeniv.linux.org.uk, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH] Documentation: document d_prune op in vfs.txt
Date: Mon, 1 Apr 2019 08:49:07 -0400 [thread overview]
Message-ID: <20190401124907.7345-1-jlayton@kernel.org> (raw)
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Documentation/filesystems/vfs.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index 761c6fd24a53..4f1638e5f95b 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -1013,6 +1013,7 @@ struct dentry_operations {
int (*d_delete)(const struct dentry *);
int (*d_init)(struct dentry *);
void (*d_release)(struct dentry *);
+ void (*d_prune)(struct dentry *);
void (*d_iput)(struct dentry *, struct inode *);
char *(*d_dname)(struct dentry *, char *, int);
struct vfsmount *(*d_automount)(struct path *);
@@ -1087,6 +1088,9 @@ struct dentry_operations {
d_release: called when a dentry is really deallocated
+ d_prune: called prior to pruning (i.e. unhashing and killing) a hashed
+ dentry from the dcache.
+
d_iput: called when a dentry loses its inode (just prior to its
being deallocated). The default when this is NULL is that the
VFS calls iput(). If you define this method, you must call
--
2.20.1
reply other threads:[~2019-04-01 12:49 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=20190401124907.7345-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).