From: Al Viro <viro@zeniv.linux.org.uk>
Date: Tue, 15 Feb 2011 06:42:59 +0000 (-0500)
Subject: get rid of nameidata_dentry_drop_rcu() calling nameidata_drop_rcu()
X-Git-Tag: firefly_0821_release~7613^2~2440^2
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=4e924a4f53a0e1ea060bd50695a12a238b250322;p=firefly-linux-kernel-4.4.55.git

get rid of nameidata_dentry_drop_rcu() calling nameidata_drop_rcu()

can't happen anymore and didn't work right anyway

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---

diff --git a/fs/namei.c b/fs/namei.c
index 10635d329175..9e701e28a329 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -455,14 +455,6 @@ static int nameidata_dentry_drop_rcu(struct nameidata *nd, struct dentry *dentry
 	struct fs_struct *fs = current->fs;
 	struct dentry *parent = nd->path.dentry;
 
-	/*
-	 * It can be possible to revalidate the dentry that we started
-	 * the path walk with. force_reval_path may also revalidate the
-	 * dentry already committed to the nameidata.
-	 */
-	if (unlikely(parent == dentry))
-		return nameidata_drop_rcu(nd);
-
 	BUG_ON(!(nd->flags & LOOKUP_RCU));
 	if (nd->root.mnt) {
 		spin_lock(&fs->lock);