summaryrefslogtreecommitdiff
path: root/sound/last.c
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2007-05-17 00:53:28 +0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2007-07-11 07:40:48 +0400
commit75180df2ed467866ada839fe73cf7cc7d75c0a22 (patch)
tree35966d0b22e58cc49ddee5b5f8d0e64c577dc576 /sound/last.c
parent8007122520f0a3599bdc4df47358a5d83b2574aa (diff)
downloadlinux-75180df2ed467866ada839fe73cf7cc7d75c0a22.tar.xz
NFS: Add the mount option "nosharecache"
Prior to David Howell's mount changes in 2.6.18, users who mounted different directories which happened to be from the same filesystem on the server would get different super blocks, and hence could choose different mount options. As long as there were no hard linked files that crossed from one subtree to another, this was quite safe. Post the changes, if the two directories are on the same filesystem (have the same 'fsid'), they will share the same super block, and hence the same mount options. Add a flag to allow users to elect not to share the NFS super block with another mount point, even if the fsids are the same. This will allow users to set different mount options for the two different super blocks, as was previously possible. It is still up to the user to ensure that there are no cache coherency issues when doing this, however the default behaviour will be to share super blocks whenever two paths result in the same fsid. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'sound/last.c')
0 files changed, 0 insertions, 0 deletions