I have some folks unhappy about behavior changes after: 479219218fbe NFS: Optimise away the close-to-open GETATTR when we have NFSv4 OPEN Before this change, a client holding a RO open would invalidate the pagecache when doing a second RW open. Now the client doesn't invalidate the pagecache, though technically it could because we see a changeattr update on the RW OPEN response. I feel this is a grey area in CTO if we're already holding an open. Do we know how the client ought to behave in this case? Should the client's open upgrade to RW invalidate the pagecache? Ben
