[GFS2] patch to check for recursive lock requests in gfs2_rename code path
authorAbhijith Das <adas@redhat.com>
Thu, 29 Nov 2007 20:13:54 +0000 (14:13 -0600)
committerSteven Whitehouse <swhiteho@redhat.com>
Fri, 25 Jan 2008 08:08:18 +0000 (08:08 +0000)
commit292c8c14cace19c94c6abe25506310239daf949e
tree3b1b1407e00abc154768dc2f5a684b0fcf0cbd1f
parentc97bfe4351771675963e02f34d31e206fd2d7150
[GFS2] patch to check for recursive lock requests in gfs2_rename code path

A certain scenario in the rename code path triggers a kernel BUG()
because it accidentally does recursive locking The first lock is
requested to unlink an already existing inode (replacing a file) and the
second lock is requested when the destination directory needs to alloc
some space. It is rare that these two
events happen during the same rename call, and even more rare that these
two instances try to lock the same rgrp. It is, however, possible.
https://bugzilla.redhat.com/show_bug.cgi?id=404711

Signed-off-by: Abhijith Das <adas@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/gfs2/rgrp.c