commit 1d6f142af885aa500084a4e96977ce32d3bad1b9
Author: Erez_Zadok <[EMAIL PROTECTED]>
Date:   Fri Jun 29 02:02:42 2007 -0400

    Unionfs: improved comment above unionfs_follow_link
    
    Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>

diff --git a/fs/unionfs/inode.c b/fs/unionfs/inode.c
index 
c8fc14a30146cff85a3bab036ecea1fcd984d138..401c62ba7a5e7709751aaf3a581de59a6cf14f24
 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)
 {
_______________________________________________
unionfs-cvs mailing list: http://unionfs.filesystems.org/
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs-cvs

Reply via email to