commit | beb2a5ec386e5ce6891ebd1c06b913da04354b40 | [log] [tgz] |
---|---|---|
author | Trond Myklebust <Trond.Myklebust@netapp.com> | Tue Jan 03 09:55:37 2006 +0100 |
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | Fri Jan 06 14:58:51 2006 -0500 |
tree | 370e0065936e5739de638389af6c85ee960a6b28 | |
parent | 969b7f2522c90dfed5d0d2553a91522bda2c3bf3 [diff] |
NFSv4: Ensure change attribute returned by GETATTR callback conforms to spec According to RFC3530 we're supposed to cache the change attribute at the time the client receives a write delegation. If the inode is clean, a CB_GETATTR callback by the server to the client is supposed to return the cached change attribute. If, OTOH, the inode is dirty, the client should bump the cached change attribute by 1. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>