What does the client do to its cache when it writes to a locked range? The RFC: https://tools.ietf.org/html/rfc7530#section-10.3.2 seems to apply that you should get something like local-filesystem semantics if you write-lock any range that you write to and read-lock any range that you read from. But I see a report that when applications write to non-overlapping ranges (while taking locks over those ranges), they don't see each other's updates. I think for simultaneous non-overlapping writes to work that way, the client would need to invalidate its cache on unlock (except for the locked range). But i can't tell what the client's designed to do. --b.
