Fix FUSE_CAP_DIRECT_IO_ALLOW_MMAP - use new numerical value

Commit 22741f5  accidentally re-used (1 << 27), which is
already taken for FUSE_CAP_SETXATTR_EXT.

Fortunately not part of any release yet.

diff --git a/include/fuse_common.h b/include/fuse_common.h
index bdbd7cb346417d6c36b7ef7072ea4e256468bb5c..52b691a5298c180034b4f5b5d78ca773eb6b7b54 100644 (file)
--- a/include/fuse_common.h
+++ b/include/fuse_common.h
@@ -445,7 +445,7 @@ struct fuse_loop_config_v1 {
  * ensure coherency between mount points (or network clients) and with kernel page
  * cache as enforced by mmap that cannot be guaranteed anymore.
  */
-#define FUSE_CAP_DIRECT_IO_ALLOW_MMAP  (1 << 27)
+#define FUSE_CAP_DIRECT_IO_ALLOW_MMAP  (1 << 28)
 
 /**
  * Ioctl flags