summaryrefslogtreecommitdiffstats
path: root/usr
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2007-07-06 10:53:21 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2007-07-10 23:40:48 -0400
commit6f2e64d3e1f661095e274c9d9d47e3f39a6cf1c0 (patch)
tree59bb802bfe2df34ef5666a3d9b7a8f7c21b7247b /usr
parent275a5d24bf56b2d9dd4644c54a56366b89a028f1 (diff)
downloadkernel-crypto-6f2e64d3e1f661095e274c9d9d47e3f39a6cf1c0.tar.gz
kernel-crypto-6f2e64d3e1f661095e274c9d9d47e3f39a6cf1c0.tar.xz
kernel-crypto-6f2e64d3e1f661095e274c9d9d47e3f39a6cf1c0.zip
NFSv4: Make the NFS state model work with the nosharedcache mount option
Consider the case where the user has mounted the remote filesystem server:/foo on the two local directories /bar and /baz using the nosharedcache mount option. The files /bar/file and /baz/file are represented by different inodes in the local namespace, but refer to the same file /foo/file on the server. Consider the case where a process opens both /bar/file and /baz/file, then closes /bar/file: because the nfs4_state is not shared between /bar/file and /baz/file, the kernel will see that the nfs4_state for /bar/file is no longer referenced, so it will send off a CLOSE rpc call. Unless the open_owners differ, then that CLOSE call will invalidate the open state on /baz/file too. Conclusion: we cannot share open state owners between two different non-shared mount instances of the same filesystem. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions