From: Erez_Zadok <ezk@cs.sunysb.edu>
Date: Fri, 29 Jun 2007 06:02:42 +0000 (-0400)
Subject: Unionfs: improved comment above unionfs_follow_link
X-Git-Url: https://git.fsl.cs.sunysb.edu/?a=commitdiff_plain;h=3f246e3bcbfe15110c142d7b489ae741dbd574c6;p=unionfs-3.1.y.git

Unionfs: improved comment above unionfs_follow_link

Signed-off-by: Erez Zadok <ezk@cs.sunysb.edu>
---

diff --git a/fs/unionfs/inode.c b/fs/unionfs/inode.c
index 384800ca2fd..b2c021445e0 100644
--- a/fs/unionfs/inode.c
+++ b/fs/unionfs/inode.c
@@ -908,9 +908,9 @@ out:
  * unionfs_readlink *does* lock our dentry and revalidate the dentry.
  * Therefore, we do not have to lock our dentry here, to prevent a deadlock;
  * nor do we need to revalidate it either.  It is safe to not lock our
- * dentry here because unionfs_follow_link does not do anything (prior to
- * calling ->readlink) which could become inconsistent due to branch
- * management.
+ * dentry here, nor revalidate it, because unionfs_follow_link does not do
+ * anything (prior to calling ->readlink) which could become inconsistent
+ * due to branch management.
  */
 static void *unionfs_follow_link(struct dentry *dentry, struct nameidata *nd)
 {