Recommend when to use -o default_permissions automatically

diff --git a/doc/mount.fuse.8 b/doc/mount.fuse.8
index 26618ca9c30e2af04a8b2d3ef8e9373ba8abe35e..ada4b0768ab798c58e8d6121d883e6e251bfa406 100644 (file)
--- a/doc/mount.fuse.8
+++ b/doc/mount.fuse.8
@@ -59,6 +59,9 @@ check (based on mode bits and ownership of the directory entry, and
 uid/gid of the client). If the filesystem supports extended
 attributes and the kernel is sufficiently recent, it may also take
 into account access control lists (ACLs).
+
+Filesystems that do not implement any permission checking should
+generally add this option internally.
 .TP
 \fBallow_other\fP
 This option overrides the security measure

diff --git a/include/fuse.h b/include/fuse.h
index 312818e8430a98ae09838a19aff81c241ec50a47..ff1475dc3228cb4e318e229dabf2c1446a67c669 100644 (file)
--- 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.

diff --git a/include/fuse_lowlevel.h b/include/fuse_lowlevel.h
index f876975ed40d8210ca73011242aea9591cc8bab1..503b682f6c2796002646c8381f53a8d910f618e6 100644 (file)
--- a/include/fuse_lowlevel.h
+++ b/include/fuse_lowlevel.h
@@ -154,6 +154,12 @@ struct fuse_forget_data {
  * after the call has returned, so if they are needed later, their
  * contents have to be copied.
  *
+ * 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_session_new()`. In this case, methods will only be called if
+ * the kernel's permission check has succeeded.
+ *
  * The filesystem sometimes needs to handle a return value of -ENOENT
  * from the reply function, which means, that the request was
  * interrupted, and the reply discarded.  For example if