From: Bernd Schubert <bschubert@ddn.com>
Date: Wed, 27 Mar 2024 19:23:12 +0000 (+0100)
Subject: Fix FUSE_CAP_DIRECT_IO_ALLOW_MMAP - use new numerical value
X-Git-Tag: fuse-3.17.1-rc0~136
X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=67d4db405059f83d3c2f4ee577a712c424b481db;p=qemu-gpiodev%2Flibfuse.git

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 bdbd7cb..52b691a 100644
--- 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