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)
committerSasha Levin <sasha.levin@oracle.com>
Thu, 21 Jan 2016 16:23:29 +0000 (11:23 -0500)
commit2de7d46289702bcc5727cb70857f8f6860c85ce8
treef3e66daca79fd48fc4c64f422c0aa51155a053d8
parentd48e82da8b064ed3ce8bfa2d8b17d8566e811f4f
nfs: if we have no valid attrs, then don't declare the attribute cache valid

[ Upstream commit c812012f9ca7cf89c9e1a1cd512e6c3b5be04b85 ]

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>
Cc: stable@vger.kernel.org
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
fs/nfs/inode.c