[Cluster-devel] [PATCH][GFS2] GFS2 - patch to check for recursive lock requests in gfs2_rename code path

[Cluster-devel] [PATCH][GFS2] GFS2 - patch to check for recursive lock requests in gfs2_rename code path

[Abhijith Das]

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>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz404711-git.patch
Type: text/x-patch
Size: 2092 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20071129/2dabff10/attachment.bin>

[Cluster-devel] Re: [PATCH][GFS2] GFS2 - patch to check for recursive lock requests in gfs2_rename code path

[Steven Whitehouse]

Hi,

On Thu, 2007-11-29 at 14:13 -0600, Abhijith Das wrote:
> 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>

Applied to the -nmw git tree. Thanks,

Steve.