summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNikolaus Rath <Nikolaus@rath.org>2016-02-01 09:08:26 -0800
committerNikolaus Rath <Nikolaus@rath.org>2016-02-01 09:09:11 -0800
commit9775c70da5f3d8214e91adf4184960d5dd68e845 (patch)
tree3702536af5f20c442f84f4725f0cdba86c7a9d91
parent6c60e26c6033b43f58af077dcd8b343545b4190d (diff)
downloadfuse-9775c70da5f3d8214e91adf4184960d5dd68e845.tar.gz
Document bug #15.
-rw-r--r--README.md14
1 files changed, 12 insertions, 2 deletions
diff --git a/README.md b/README.md
index b3ed5b1..9274d7b 100644
--- a/README.md
+++ b/README.md
@@ -57,8 +57,18 @@ doing nasty things. Currently those limitations are:
- The mountpoint is not a sticky directory which isn't owned by the
user (like /tmp usually is)
- - No other user (including root) can access the contents of the mounted
- filesystem (though this can be relaxed)
+ - No other user (including root) can access the contents of the
+ mounted filesystem (though this can be relaxed by allowing the use
+ of the `allow_other` and `allow_root` mount options in `fuse.conf`)
+
+When using the `allow_other` option, be aware of
+[bug #15](https://github.com/libfuse/libfuse/issues/15): the
+permission to access a cached directory entry is only checked for the
+first user that accesses it. As long as the directory entry is cached,
+accesses by other users are made with the permissions of the first
+user. The only work around for this bug is to disable caching of
+directory entries, or to not use `allow_other`.
+
Building your own filesystem