summaryrefslogtreecommitdiff
path: root/fs/romfs
diff options
context:
space:
mode:
authorBob Peterson <rpeterso@redhat.com>2008-06-09 21:08:23 +0400
committerSteven Whitehouse <swhiteho@redhat.com>2008-06-27 12:39:41 +0400
commit9171f5a991e7613cbee816874ad8c9515dcab50f (patch)
tree6fd5df32583c059344f7ec4b9436b68edecd61c0 /fs/romfs
parent01b7c7ae88a6376c508b35a22bb61e04cb1b37f0 (diff)
downloadlinux-9171f5a991e7613cbee816874ad8c9515dcab50f.tar.xz
[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/romfs')
0 files changed, 0 insertions, 0 deletions