On Mon, 12 May 2014 13:58:59 -0700 Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> wrote: > > On May 11, 2014, at 20:50, NeilBrown <neilb@xxxxxxx> wrote: > > > > > > > NFS CTO semantics require that (absent a delegation) the server > > must be contacted at each open. > > > > nfs_lookup_verify_inode() implements this when the dcache contains > > a positive cached entry. However it is not called when the dcache > > contains a negative cached entry. That path uses nfs_neg_need_reval() > > which doesn't impose CTO semantics. > > > > So a sequence like: > > > > rm -f testfile > > ls -l testfile > > ssh $server touch testfile > > cat testfile > > > > will fail: > > > > cat: testfile: No such file or directory > > > > an 'strace' will confirm that this resulted from an 'open' system > > call. > > > > So add code to nfs_neg_need_reval implement CTO semantics much like > > that in nfs_lookup_verify_inode(). > > Hi Neil, > > To me, close-to-open is about ensuring that the data and metadata caches for the file (or directory) in question are revalidated correctly on open (or opendir). Close-to-open semantics are enabled/disabled by the cto/nocto mount options (with cto being the default). > > The lookup semantics are about ensuring that the namespace cache is consistent with what is on the server. They are controlled by the ‘lookupcache’ mount option, which defaults to the behaviour that you describe above (lookupcache=all). I believe that we have discussed changing the default to be lookupcache=positive, which would give the semantics that your patch enforces, but I believe the consensus was to keep the current behaviour. > Yes - of course. Thanks for clarifying that for me. I had in mind that lookup-for-open is special. It is, but not that special. Thanks, NeilBrown
Attachment:
signature.asc
Description: PGP signature
