aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorGravatar Nikolaus Rath <Nikolaus@rath.org>2016-10-25 20:51:04 -0700
committerGravatar Nikolaus Rath <Nikolaus@rath.org>2016-10-25 20:51:04 -0700
commit9bc565c77ef06b47ab9dc96932ad94e990564de0 (patch)
treeaa26085a449e8446fec943108b25d3abe9e895d1 /include
parente63ed532cba49ecb936cf5941bd0e9bf60efb974 (diff)
Clarify difference between notify_inval_entry and notify_delete().
Fixes #85.
Diffstat (limited to 'include')
-rw-r--r--include/fuse_lowlevel.h11
1 files changed, 8 insertions, 3 deletions
diff --git a/include/fuse_lowlevel.h b/include/fuse_lowlevel.h
index e6f95a9..f876975 100644
--- 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