aboutsummaryrefslogtreecommitdiffstats
path: root/fs/gfs2/ops_super.c
diff options
context:
space:
mode:
authorBob Peterson <rpeterso@redhat.com>2008-06-09 12:08:23 -0500
committerSteven Whitehouse <swhiteho@redhat.com>2008-06-27 09:39:41 +0100
commit9171f5a991e7613cbee816874ad8c9515dcab50f (patch)
tree6fd5df32583c059344f7ec4b9436b68edecd61c0 /fs/gfs2/ops_super.c
parent01b7c7ae88a6376c508b35a22bb61e04cb1b37f0 (diff)
downloadkernel_samsung_tuna-9171f5a991e7613cbee816874ad8c9515dcab50f.zip
kernel_samsung_tuna-9171f5a991e7613cbee816874ad8c9515dcab50f.tar.gz
kernel_samsung_tuna-9171f5a991e7613cbee816874ad8c9515dcab50f.tar.bz2
[GFS2] kernel panic mounting volume
This patch fixes Red Hat bugzilla bug 450156. This started with a not-too-improbable mount failure because the locking protocol was never set back to its proper "lock_dlm" after the system was rebooted in the middle of a gfs2_fsck. That left a (purposely) invalid locking protocol in the superblock, which caused an error when the file system was mounted the next time. When there's an error mounting, vfs calls DQUOT_OFF, which calls vfs_quota_off which calls gfs2_sync_fs. Next, gfs2_sync_fs calls gfs2_log_flush passing s_fs_info. But due to the error, s_fs_info had been previously set to NULL, and so we have the kernel oops. My solution in this patch is to test for the NULL value before passing it. I tested this patch and it fixes the problem. Signed-off-by: Bob Peterson <rpeterso@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/gfs2/ops_super.c')
-rw-r--r--fs/gfs2/ops_super.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/gfs2/ops_super.c b/fs/gfs2/ops_super.c
index 0b7cc92..6690792 100644
--- a/fs/gfs2/ops_super.c
+++ b/fs/gfs2/ops_super.c
@@ -155,7 +155,7 @@ static void gfs2_write_super(struct super_block *sb)
static int gfs2_sync_fs(struct super_block *sb, int wait)
{
sb->s_dirt = 0;
- if (wait)
+ if (wait && sb->s_fs_info)
gfs2_log_flush(sb->s_fs_info, NULL);
return 0;
}