Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=70831465646b1fef9bf7b51b64409276411e9746
Commit:     70831465646b1fef9bf7b51b64409276411e9746
Parent:     d200778e1257eeb92242355de6f191a0a5ad43c4
Author:     Robert Peterson <[EMAIL PROTECTED]>
AuthorDate: Thu Jan 11 13:25:00 2007 -0600
Committer:  Steven Whitehouse <[EMAIL PROTECTED]>
CommitDate: Mon Feb 5 13:36:46 2007 -0500

    [GFS2] gfs2 knows of directories which it chooses not to display
    
    This is for Red Hat bugzilla bug bz #222302:
    
    Moving a virtual IP from node to node between two NFS-over-GFS2
    servers was causing one of the GFS2 servers to become confused and
    reference a deleted inode.  The problem was due to vfs dentries that did
    not reference the gfs2_dops and therefore didn't call the gfs2 revalidate
    code to revalidate a dentry after a directory had been deleted & recreated.
    This patch is a crosswrite from a RHEL4 bug found in GFS1 as
    bz #190756 and it is against the latest -nmw git tree.
    
    Signed-off-by: Robert Peterson <[EMAIL PROTECTED]>
    Signed-off-by: Steven Whitehouse <[EMAIL PROTECTED]>
---
 fs/gfs2/ops_export.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/fs/gfs2/ops_export.c b/fs/gfs2/ops_export.c
index b4e7b87..6ea979c 100644
--- a/fs/gfs2/ops_export.c
+++ b/fs/gfs2/ops_export.c
@@ -22,6 +22,7 @@
 #include "glock.h"
 #include "glops.h"
 #include "inode.h"
+#include "ops_dentry.h"
 #include "ops_export.h"
 #include "rgrp.h"
 #include "util.h"
@@ -189,6 +190,7 @@ static struct dentry *gfs2_get_parent(struct dentry *child)
                return ERR_PTR(-ENOMEM);
        }
 
+       dentry->d_op = &gfs2_dops;
        return dentry;
 }
 
@@ -269,6 +271,7 @@ out_inode:
                return ERR_PTR(-ENOMEM);
        }
 
+       dentry->d_op = &gfs2_dops;
        return dentry;
 
 fail_rgd:
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to