nfs: if we have no valid attrs, then don't declare the attribute cache valid
authorJeff Layton <jlayton@poochiereds.net>
Wed, 25 Nov 2015 18:50:11 +0000 (13:50 -0500)
committerZefan Li <lizefan@huawei.com>
Wed, 26 Oct 2016 15:15:33 +0000 (23:15 +0800)
commit5cd25ba84bd375bb62ff8a8de68d3788591ecb6b
tree9d151962deb5cf74b9119ceded7a1c03d85d97bd
parenta8d3a5b24da10c5d6b7c2bc2ee26def66f9f46ec
nfs: if we have no valid attrs, then don't declare the attribute cache valid

commit c812012f9ca7cf89c9e1a1cd512e6c3b5be04b85 upstream.

If we pass in an empty nfs_fattr struct to nfs_update_inode, it will
(correctly) not update any of the attributes, but it then clears the
NFS_INO_INVALID_ATTR flag, which indicates that the attributes are
up to date. Don't clear the flag if the fattr struct has no valid
attrs to apply.

Reviewed-by: Steve French <steve.french@primarydata.com>
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Zefan Li <lizefan@huawei.com>
fs/nfs/inode.c