hi,
Does anyone know why there is different code for resolution in
fuse vs server? There are some differences too, like server asserts
about the resolution types like RESOLVE_MUST/RESOLVE_NOT etc where as
fuse doesn't do any such thing. Wondering if there is any reason why the
code is
There are subtle differences between fuse and server. In fuse the inode
table does not use LRU pruning, so expected inodes are guaranteed to be
cached. For e.g, when mkdir() FOP arrives, fuse would have already checked
with a lookup and the kernel guarantees another thread would not have
created
