Document true meaning of the 'use_ino' option.

diff --git a/ChangeLog.rst b/ChangeLog.rst
index 7b7e3c06698704168a34d5b7ccd06096c662241c..3c4c9725d4f42706f492c0c1d4aba1bc261baa8d 100644 (file)
--- a/ChangeLog.rst
+++ b/ChangeLog.rst
@@ -4,7 +4,10 @@ libfuse 3.1.0 (UNRELEASED)
 * Re-introduced examples/null.c.
 * Added experimental support for building with Meson.
 * Document that -o auto_unmount implies -o nodev,nosuid.
-
+* Document that `-o auto_unmount` implies `-o nodev,nosuid`.
+* Document that the *use_ino* option of the high-level interface does
+  not affect the inode that libfuse and the kernel use internally.
+  
 libfuse 3.0.0 (2016-12-08)
 ==========================
 

diff --git a/include/fuse.h b/include/fuse.h
index 89798eff6d056b03c2684e6df4c9340aec04753d..6bba1ce5b987e63a6f8ba450c11cf628b87c4d09 100644 (file)
--- a/include/fuse.h
+++ b/include/fuse.h
@@ -177,6 +177,9 @@ struct fuse_config {
         * field in the readdir(2) function. The filesystem does not
         * have to guarantee uniqueness, however some applications
         * rely on this value being unique for the whole filesystem.
+        *
+        * Note that this does *not* affect the inode that libfuse 
+        * and the kernel use internally (also called the "nodeid").
         */
        int use_ino;
 
@@ -292,7 +295,9 @@ struct fuse_operations {
         *
         * Similar to stat().  The 'st_dev' and 'st_blksize' fields are
         * ignored. The 'st_ino' field is ignored except if the 'use_ino'
-        * mount option is given.
+        * mount option is given. In that case it is passed to userspace,
+        * but libfuse and the kernel will still assign a different
+        * inode for internal use (called the "nodeid").
         *
         * `fi` will always be NULL if the file is not currenly open, but
         * may also be NULL if the file is open.