nfs: ensure that attrcache is revalidated after a SETATTR
authorJeff Layton <jlayton@poochiereds.net>
Wed, 25 Nov 2015 18:50:45 +0000 (13:50 -0500)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Wed, 25 Nov 2015 20:24:30 +0000 (15:24 -0500)
commit616c319683e34d10952b74a73ee12e080531b476
tree87cb8d6bb09b7be3cdfbb1bafd00958ee9fce8ce
parent38b7631fbe42e6e247e9fc9879f961b14a687e3b
nfs: ensure that attrcache is revalidated after a SETATTR

If we get no post-op attributes back from a SETATTR operation, then no
attributes will of course be updated during the call to
nfs_update_inode.

We know however that the attributes are invalid at that point, since we
just changed some of them. At the very least, the ctime will be bogus.
If we get no post-op attributes back on the call, mark the attrcache
invalid to reflect that fact.

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>
fs/nfs/inode.c