fs: don't use igrab() while holding i_lock
authorDave Chinner <dchinner@redhat.com>
Tue, 29 Mar 2011 07:08:50 +0000 (18:08 +1100)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 29 Mar 2011 14:50:34 +0000 (07:50 -0700)
Fix the incorrect use of igrab() inside the i_lock in NFS and Ceph‥

If we are already holding the i_lock, we have a reference to the
inode so we can safely use ihold() to gain an extra reference. This
avoids hangs due to lock recursion on the i_lock now that the
inode_lock is gone and igrab() uses the i_lock itself.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Cc: Ryan Mallon <ryan@bluewatersys.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

No differences found