summaryrefslogtreecommitdiffstats
path: root/fs/sysv/CHANGES
diff options
context:
space:
mode:
authorMiklos Szeredi <miklos@szeredi.hu>2006-10-17 00:10:11 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2006-10-17 08:18:45 -0700
commitd2a85164aaa8d514ef5efbf5d05746e85dd13ddd (patch)
tree82a10eff007860a9bfc515d037cc2fea6c999bc0 /fs/sysv/CHANGES
parent265126ba9e1f8e217e61d1017c6609f76828aa7a (diff)
downloadblackbird-op-linux-d2a85164aaa8d514ef5efbf5d05746e85dd13ddd.tar.gz
blackbird-op-linux-d2a85164aaa8d514ef5efbf5d05746e85dd13ddd.zip
[PATCH] fuse: fix handling of moved directory
Fuse considered it an error (EIO) if lookup returned a directory inode, to which a dentry already refered. This is because directory aliases are not allowed. But in a network filesystem this could happen legitimately, if a directory is moved on a remote client. This patch attempts to relax the restriction by trying to first evict the offending alias from the cache. If this fails, it still returns an error (EBUSY). A rarer situation is if an mkdir races with an indenpendent lookup, which finds the newly created directory already moved. In this situation the mkdir should return success, but that would be incorrect, since the dentry cannot be instantiated, so return EBUSY. Previously checking for a directory alias and instantiation of the dentry weren't done atomically in lookup/mkdir, hence two such calls racing with each other could create aliased directories. To prevent this introduce a new per-connection mutex: fuse_conn->inst_mutex, which is taken for instantiations with a directory inode. Signed-off-by: Miklos Szeredi <miklos@szeredi.hu> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/sysv/CHANGES')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud