cluster: RHEL510 - fsck.gfs2: fsck.gfs2: Sync di_nlink adding links for lost+found

[Bob Peterson]

Gitweb:        http://git.fedorahosted.org/git/?p=cluster.git;a=commitdiff;h=dce22ab145195e...
Commit:        dce22ab145195e3f27b9a22f66181e914da4644d
Parent:        df252765275ed2f0c2e96a90c174e3d933d4945f
Author:        Bob Peterson 
AuthorDate:    Mon Aug 8 14:21:06 2011 -0500
Committer:     Bob Peterson 
CommitterDate: Fri Apr 5 06:24:59 2013 -0700

fsck.gfs2: fsck.gfs2: Sync di_nlink adding links for lost+found

When adding a ".." entry to a directory newly linked to lost+found
fsck.gfs2 needs to update its di_nlink value to account for the new
link.  If not, it can "correct" the di_nlink value to the wrong
value and not find the error until a second fsck.gfs2 is done.
This only happens in the rare case where there is no pre-existing
".." entry that may be reused to re-link to lost+found.

rhbz#877150
---
 gfs2/fsck/lost_n_found.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/gfs2/fsck/lost_n_found.c b/gfs2/fsck/lost_n_found.c
index 4ef4fb9..cfc3d07 100644
--- a/gfs2/fsck/lost_n_found.c
+++ b/gfs2/fsck/lost_n_found.c
@@ -122,6 +122,7 @@ int add_inode_to_lf(struct gfs2_inode *ip){
    		dip = fsck_load_inode(sdp, di->dotdot_parent);
    		if (dip->i_di.di_nlink > 0) {
    			dip->i_di.di_nlink--;
+				set_di_nlink(dip); /* keep inode tree in sync */
    			log_debug(_("Decrementing its links to %d\n"),
    				  dip->i_di.di_nlink);
    			bmodified(dip->i_bh);
@@ -132,6 +133,7 @@ int add_inode_to_lf(struct gfs2_inode *ip){
    				    "Changing it to 0.\n"),
    				  dip->i_di.di_nlink);
    			dip->i_di.di_nlink = 0;
+				set_di_nlink(dip); /* keep inode tree in sync */
    			bmodified(dip->i_bh);
    		}
    		fsck_inode_put(&dip);