add documentation

diff --git a/include/fuse.h b/include/fuse.h
index 84c03410645da889b5ba22e9415fe645deb0e6c5..d16135e12c72bfeeb7a4e9f1e59ee375d44fdb38 100644 (file)
--- a/include/fuse.h
+++ b/include/fuse.h
@@ -185,6 +185,9 @@ struct fuse_operations {
      * should be treated equally.  Multiple write-flush sequences are
      * relatively rare, so this shouldn't be a problem.
      *
+     * Filesystems shouldn't assume that flush will allways be called
+     * after some writes, or that if will be called at all.
+     *
      * Changed in version 2.2
      */
     int (*flush) (const char *, struct fuse_file_info *);

diff --git a/include/fuse_lowlevel.h b/include/fuse_lowlevel.h
index 02e3806b7d4bf7358978e602ae4f672ebc1030fd..93712f58984f1f9f39d39956972cfb6e296e13df 100644 (file)
--- a/include/fuse_lowlevel.h
+++ b/include/fuse_lowlevel.h
@@ -412,6 +412,9 @@ struct fuse_lowlevel_ops {
      * Since file descriptors can be duplicated (dup, dup2, fork), for
      * one open call there may be many flush calls.
      *
+     * Filesystems shouldn't assume that flush will allways be called
+     * after some writes, or that if will be called at all.
+     *
      * fi->fh will contain the value set by the open method, or will
      * be undefined if the open method didn't set any value.
      *