summaryrefslogtreecommitdiffstats
path: root/fs/gfs2
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2007-02-28 14:03:00 +0000
committerSteven Whitehouse <swhiteho@redhat.com>2007-03-07 14:00:14 -0500
commitcad5b9392754910ee7dbe551eb004010a864c882 (patch)
tree8f471553844c6a920d607a82b466f649599a102e /fs/gfs2
parentfb0d3bce8e88cca4abb26076f778f64edcaf19aa (diff)
downloadlinux-cad5b9392754910ee7dbe551eb004010a864c882.tar.gz
linux-cad5b9392754910ee7dbe551eb004010a864c882.tar.bz2
linux-cad5b9392754910ee7dbe551eb004010a864c882.zip
[GFS2] Fix bz 230143, incorrect flushing of rgrps
The below patch fixes a problem where we were not flushing rgrps correctly. It only occurred in the specific case that a callback was received for an rgrp which was dirty and when a journal log flush had not already resulted in the rgrp being flushed anyway. This fixes Red Hat bz 230143, Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/gfs2')
-rw-r--r--fs/gfs2/glops.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/gfs2/glops.c b/fs/gfs2/glops.c
index 46af55355513..42211105c3f8 100644
--- a/fs/gfs2/glops.c
+++ b/fs/gfs2/glops.c
@@ -459,6 +459,8 @@ const struct gfs2_glock_operations gfs2_inode_glops = {
};
const struct gfs2_glock_operations gfs2_rgrp_glops = {
+ .go_xmote_th = meta_go_sync,
+ .go_drop_th = meta_go_sync,
.go_inval = meta_go_inval,
.go_demote_ok = rgrp_go_demote_ok,
.go_lock = rgrp_go_lock,