diff options
author | Trond Myklebust <trond.myklebust@primarydata.com> | 2014-02-06 14:38:53 -0500 |
---|---|---|
committer | Trond Myklebust <trond.myklebust@primarydata.com> | 2014-02-10 08:44:12 -0500 |
commit | fd1defc257e2b12ab69bc0b379105c00eca4e112 (patch) | |
tree | f0058b38b262aacd30da1ac5e4e85fb37451f559 /net/sunrpc/auth_gss/auth_gss.c | |
parent | b28a960c42fcd9cfc987441fa6d1c1a471f0f9ed (diff) | |
download | linux-fd1defc257e2b12ab69bc0b379105c00eca4e112.tar.gz linux-fd1defc257e2b12ab69bc0b379105c00eca4e112.tar.bz2 linux-fd1defc257e2b12ab69bc0b379105c00eca4e112.zip |
NFS: Do not set NFS_INO_INVALID_LABEL unless server supports labeled NFS
Commit aa9c2669626c (NFS: Client implementation of Labeled-NFS) introduces
a performance regression. When nfs_zap_caches_locked is called, it sets
the NFS_INO_INVALID_LABEL flag irrespectively of whether or not the
NFS server supports security labels. Since that flag is never cleared,
it means that all calls to nfs_revalidate_inode() will now trigger
an on-the-wire GETATTR call.
This patch ensures that we never set the NFS_INO_INVALID_LABEL unless the
server advertises support for labeled NFS.
It also causes nfs_setsecurity() to clear NFS_INO_INVALID_LABEL when it
has successfully set the security label for the inode.
Finally it gets rid of the NFS_INO_INVALID_LABEL cruft from nfs_update_inode,
which has nothing to do with labeled NFS.
Reported-by: Neil Brown <neilb@suse.de>
Cc: stable@vger.kernel.org # 3.11+
Tested-by: Neil Brown <neilb@suse.de>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'net/sunrpc/auth_gss/auth_gss.c')
0 files changed, 0 insertions, 0 deletions