NFSv4: Add 'server capability' flags for NFSv4 recommended attributes
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Sun, 9 Aug 2009 19:06:19 +0000 (15:06 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Sun, 9 Aug 2009 19:06:19 +0000 (15:06 -0400)
commit62ab460cf5e450e1d207a98a9c6cf2e4a6a78fd1
tree595ca70261f46b93bda1998285e5f5c7da684cbc
parenta78cb57a106fceeba26da2907db9d8886700e1dc
NFSv4: Add 'server capability' flags for NFSv4 recommended attributes

If the NFSv4 server doesn't support a POSIX attribute, the generic NFS code
needs to know that, so that it don't keep trying to poll for it.

However, by the same count, if the NFSv4 server does support that
attribute, then we should ensure that the inode metadata is appropriately
labelled as being untrusted. For instance, if we don't know the correct
value of the file's uid, we should certainly not be caching ACLs or ACCESS
results.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/client.c
fs/nfs/inode.c
fs/nfs/nfs4proc.c
include/linux/nfs_fs_sb.h