Is kernel oplocks = yes a good default?

[J. Bruce Fields]

On Thu, Apr 12, 2012 at 01:32:09PM -0400, J. Bruce Fields wrote:
> On Thu, Apr 12, 2012 at 06:45:11PM +0200, Christian Ambach wrote:
> > But Windows revokes them on some more occasions, e.g. if byte-range
> > locks are requested on a file,
> 
> You wouldn't be able to get a write (exclusive) lock on a read-delegated
> file.  We don't bother stating that, though, just because you wouldn't
> be able to get a write lock without getting a write open first, and that
> would have already broken the delegation.
> 
> That results in a delegation recall for NFSv4 as well.  But we don't
> need to say that, because you can't get a conflicting byte range lock
> without first getting a conflicting open.

(Looks like sometimes I rewrite a paragraph and then leave the original
version in there.  Hey, read whichever one you like best!)

--b.