From: Oleg Drokin <green@linuxhacker.ru>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Oleg Drokin <green@linuxhacker.ru>
Subject: [PATCH] Remove stale d_splice_alias comment
Date: Mon, 20 Jun 2016 11:22:46 -0400 [thread overview]
Message-ID: <1466436166-2122976-1-git-send-email-green@linuxhacker.ru> (raw)
It's not really possible to call d_splice_alias with a hashed
dentry no matter what, so remove the stale comment indicating
otherwise. The only user of this functionality was fixed
long ago according to Al.
Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
---
Catching this up before it gets forgotten again and confuses somebody else
fs/dcache.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/fs/dcache.c b/fs/dcache.c
index 817c243..f7a76e1 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -2961,7 +2961,7 @@ out_err:
/**
* d_splice_alias - splice a disconnected dentry into the tree if one exists
* @inode: the inode which may have a disconnected dentry
- * @dentry: a negative dentry which we want to point to the inode.
+ * @dentry: a negative unhashed dentry which we want to point to the inode.
*
* If inode is a directory and has an IS_ROOT alias, then d_move that in
* place of the given dentry and return it, else simply d_add the inode
@@ -2975,11 +2975,6 @@ out_err:
*
* If a dentry was found and moved, then it is returned. Otherwise NULL
* is returned. This matches the expected return value of ->lookup.
- *
- * Cluster filesystems may call this function with a negative, hashed dentry.
- * In that case, we know that the inode will be a regular file, and also this
- * will only occur during atomic_open. So we need to check for the dentry
- * being already hashed only in the final case.
*/
struct dentry *d_splice_alias(struct inode *inode, struct dentry *dentry)
{
--
2.7.4
reply other threads:[~2016-06-20 16:04 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=1466436166-2122976-1-git-send-email-green@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome