Hello,
I just added an example to FUSE that illustrates use of the
fuse_lowlevel_notify_inval_entry() function. However, when writing it I
realized that I don't actually fully understand how this function
differs from fuse_lowlevel_notify_delete(). Could someone shed some
light on this?
Currently, the FUSE documentation says:
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?
Thanks,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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
