Detect the case where rename()ing over a file that has been unlinked but
authorMatthew Dillon <dillon@dragonflybsd.org>
Tue, 31 Jul 2007 01:16:53 +0000 (01:16 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Tue, 31 Jul 2007 01:16:53 +0000 (01:16 +0000)
commitbf6a1c3bbe683583a3fa8b597cee021f50b016e7
tree1dbc57e74c3f00db97d56d8e262c1410364c59c0
parent5954ac0724046aea99de108fdb55d5f8ec875f09
Detect the case where rename()ing over a file that has been unlinked but
is still open was reporting an inode hash collision instead of a fatal
error.  msdosfs uses the position of the directory entry within the directory
to identify the inode and a new file cannot be created if the removed file
is still held open by a program.

Reported-by: walt <wa1ter@myrealbox.com>
sys/vfs/msdosfs/msdosfs_denode.c