Restore compat ABI in 'struct fuse_file_info'

This fixes commit
a5eb7f2 "Enable parallel direct writes on the same file"
and restores the ABI by moving the parallel_direct_writes
bit.

Given that there were already several releases with this commit
we will still need an so version bump.

Signed-off-by: Bernd Schubert <bernd@bsbernd.com>

1 files changed, 16 insertions, 15 deletions

diff --git a/include/fuse.h b/include/fuse.h
index 396358d..49ba7d9 100644
--- a/include/fuse.h
+++ b/include/fuse.h
@@ -281,21 +281,6 @@ struct fuse_config {
 	int nullpath_ok;
 
 	/**
-	 *  Allow parallel direct-io writes to operate on the same file.
-	 *
-	 *  FUSE implementations which do not handle parallel writes on
-	 *  same file/region should NOT enable this option at all as it
-	 *  might lead to data inconsistencies.
-	 *
-	 *  For the FUSE implementations which have their own mechanism
-	 *  of cache/data integrity are beneficiaries of this setting as
-	 *  it now open doors to parallel writes on the same file (without
-	 *  enabling this setting, all direct writes on the same file are
-	 *  serialized, resulting in huge data bandwidth loss).
-	 */
-	int parallel_direct_writes;
-
-	/**
 	 * These 3 options are used by libfuse internally and
 	 * should not be touched.
 	 */
@@ -310,6 +295,22 @@ struct fuse_config {
 	 */
 	unsigned int fmask;
 	unsigned int dmask;
+
+	/**
+	 *  Allow parallel direct-io writes to operate on the same file.
+	 *
+	 *  FUSE implementations which do not handle parallel writes on
+	 *  same file/region should NOT enable this option at all as it
+	 *  might lead to data inconsistencies.
+	 *
+	 *  For the FUSE implementations which have their own mechanism
+	 *  of cache/data integrity are beneficiaries of this setting as
+	 *  it now open doors to parallel writes on the same file (without
+	 *  enabling this setting, all direct writes on the same file are
+	 *  serialized, resulting in huge data bandwidth loss).
+	 */
+	int parallel_direct_writes;
+
 };