GFS2 - patch to check for recursive lock requests in gfs2_rename code path
PATCH 1/1 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
-------------- 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>
Steven Whitehouse
AppliedHi,
Quoted 10 lines · 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=404711Signed-off-by Abhijith Das <[email protected]>
Applied to the -nmw git tree. Thanks,
Steve.