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)
committerDanny Wood <danwood76@gmail.com>
Tue, 29 Jan 2019 13:10:59 +0000 (13:10 +0000)
commitffb67e88530cfcdd0e61bb12bb7a66225d74d481
tree62e81a6a1525b3f912ef577265b12acae514a809
parentc14f7069ebcb20f690e573bfe443911249543a14
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfs/inode.c