ocfs2: fix rename vs unlink race
authorSrinivas Eeda <srinivas.eeda@oracle.com>
Wed, 31 Oct 2007 23:49:43 +0000 (16:49 -0700)
committerMark Fasheh <mark.fasheh@oracle.com>
Tue, 6 Nov 2007 23:35:40 +0000 (15:35 -0800)
commite325a88f17196f18888f6e1426eb9fe3b4346d28
tree34536cea32f530c0a41df0b8323d1e3a2249a0e6
parentbc7e97cbdd4bef162e5772c74ee2cc4487a2d997
ocfs2: fix rename vs unlink race

If another node unlinks the destination while ocfs2_rename() is waiting on a
cluster lock, ocfs2_rename() simply logs an error and continues. This causes
a crash because the renaming node is now trying to delete a non-existent
inode. The correct solution is to return -ENOENT.

Signed-off-by: Srinivas Eeda <srinivas.eeda@oracle.com>
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
fs/ocfs2/namei.c