> On 2016.10.08, at 21:37 , Nikolaus Rath <Nikolaus@xxxxxxxx> wrote: > > fuse_lowlevel_notify_inval_entry: > Notify to invalidate parent attributes and the dentry matching > parent/name > > fuse_lowlevel_notify_delete: > Notify to invalidate parent attributes and delete the dentry matching > parent/name if the dentry's inode number matches child (otherwise it > will invalidate the matching dentry). > > > But what exactly is the difference between deleting and invalidating a > dentry? In each case, isn't the resulting behavior the same, in that the > next time someone tries to access this (parent_inode,entry_name) > combination a lookup() request will be send to the FUSE process? These are aimed at networked file-systems where changes can be initiated at the other end. The first clears the cached data for that dentry, so that next time the file lookup occurs the file is still in existence but there is no cached data, forcing the request to go down to the user-space file-system. This would be used during remote rename. The second actually removes the dentry in the VFS in the kernel. This would be used during remote deletion. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
