Clarify difference between notify_inval_entry and notify_delete().

Fixes #85.

diff --git a/include/fuse_lowlevel.h b/include/fuse_lowlevel.h
index e6f95a99ea6262eb3b7d95e095621f598980c521..f876975ed40d8210ca73011242aea9591cc8bab1 100644 (file)
--- a/include/fuse_lowlevel.h
+++ b/include/fuse_lowlevel.h
@@ -1439,9 +1439,14 @@ int fuse_lowlevel_notify_inval_entry(struct fuse_session *se, fuse_ino_t parent,
                                     const char *name, size_t namelen);
 
 /**
- * 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).
+ * As of kernel 4.8, this function behaves like
+ * fuse_lowlevel_notify_inval_entry() with the following additional
+ * effect:
+ *
+ * If the provided *child* inode matches the inode that is currently
+ * associated with the cached dentry, and if there are any inotify
+ * watches registered for the dentry, then the watchers are informed
+ * that the dentry has been deleted.
  *
  * To avoid a deadlock don't call this function from a filesystem operation and
  * don't call it with a lock held that can also be held by a filesystem