From: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> The changes to allow more fine grained revalidation of the inode attribute cache has had a detrimental effect on the polling timeouts. The current code assumes that if we've not revalidated all the attributes in the cache, then we can't advance the polling window. That's obviously incorrect. What we really want is to ensure that if we've revalidated the cache by checking the value of the change attribute against the server value, then we can update the polling window timer. Trond Myklebust (3): NFS: Fix up inode attribute revalidation timeouts NFSv4: Fix handling of non-atomic change attrbute updates NFS: Avoid duplicate resets of attribute cache timeouts fs/nfs/inode.c | 57 ++++++++++++++--------------------------------- fs/nfs/nfs4proc.c | 33 +++++++++++++-------------- 2 files changed, 32 insertions(+), 58 deletions(-) -- 2.31.1
