diff options
author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-10-15 18:17:53 -0400 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-10-19 17:19:16 -0400 |
commit | 565277f63c616e11c37309a1e98c052d18ebbb55 (patch) | |
tree | 60fdddc5a1c97df696392e47ead71d33d39e487f /fs/bad_inode.c | |
parent | 61e930a904966cc37e0a3404276f0b73037e57ca (diff) | |
download | op-kernel-dev-565277f63c616e11c37309a1e98c052d18ebbb55.zip op-kernel-dev-565277f63c616e11c37309a1e98c052d18ebbb55.tar.gz |
NFS: Fix a race in sillyrename
lookup() and sillyrename() can race one another because the sillyrename()
completion cannot take the parent directory's inode->i_mutex since the
latter may be held by whoever is calling dput().
We therefore have little option but to add extra locking to ensure that
nfs_lookup() and nfs_atomic_open() do not race with the sillyrename
completion.
If somebody has looked up the sillyrenamed file in the meantime, we just
transfer the sillydelete information to the new dentry.
Please refer to the bug-report at
http://bugzilla.linux-nfs.org/show_bug.cgi?id=150
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/bad_inode.c')
0 files changed, 0 insertions, 0 deletions