Recommend when to use -o default_permissions automatically

1 files changed, 6 insertions, 6 deletions

diff --git a/include/fuse.h b/include/fuse.h
index 312818e..ff1475d 100644
--- a/include/fuse.h
+++ b/include/fuse.h
@@ -280,13 +280,13 @@ struct fuse_config {
  * init and destroy are special purpose methods, without which a full
  * featured filesystem can still be implemented.
  *
- * Almost all operations take a path which can be of any length.
- *
- * Changed in fuse 2.8.0 (regardless of API version)
- * Previously, paths were limited to a length of PATH_MAX.
+ * In general, all methods are expected to perform any necessary
+ * permission checking. However, a filesystem may delegate this task
+ * to the kernel by passing the `default_permissions` mount option to
+ * `fuse_new()`. In this case, methods will only be called if
+ * the kernel's permission check has succeeded.
  *
- * See http://fuse.sourceforge.net/wiki/ for more information.  There
- * is also a snapshot of the relevant wiki pages in the doc/ folder.
+ * Almost all operations take a path which can be of any length.
  */
 struct fuse_operations {
 	/** Get file attributes.