On Tue, 2017-09-26 at 13:31 +0000, Sage Weil wrote: > On Tue, 26 Sep 2017, Jeff Layton wrote: > > In order to get the correct semantics for a delegation or oplock, > we > > need to be able to break delegations on open. > > Can you explain this part? How do the delegation/oplock semantics > relate > to open(2)? I would assume they are related to reads and writes (and > data > consistency). Unless it's a CIFS thing? You're correct that we only really need to break delegations on conflicting access, but there is a problem here: NFS clients can cache shared/deny mode locks if they hold a delegation. Once you've granted an open, it's too late to go back and enforce it once you go to recall the delegation. Since we don't enforce deny mode locks in cephfs, we could argue that all of that is the purview of the NFS server and not worry about it...at least until we toss something like samba into the mix, at which point things get a bit more complicated... -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
