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)
committerWilly Tarreau <w@1wt.eu>
Fri, 29 Jan 2016 21:12:46 +0000 (22:12 +0100)
commit86ba50116c357109d57300ff08bf4ee66463cae3
treea17d9a0badaa34749e288870b756dd9aebff81e9
parent74147da1b621c713937081929a7ffc175e9c4691
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: Ben Hutchings <ben@decadent.org.uk>
(cherry picked from commit ddab0155aa9589600861e3f65d505982b719496a)
Signed-off-by: Willy Tarreau <w@1wt.eu>
fs/nfs/inode.c