From ee0b29552ae92a6d991b02c778377fda6bfbfac5 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Wed, 15 Mar 2017 16:44:35 -0700 Subject: open(): fix documentation of O_TRUNC flag The FUSE_CAP_ATOMIC_IO_TRUNC capability is enabled by default, but we didn't update the open() documentation accordingly. --- include/fuse_common.h | 4 +++- include/fuse_lowlevel.h | 10 ++-------- 2 files changed, 5 insertions(+), 9 deletions(-) (limited to 'include') diff --git a/include/fuse_common.h b/include/fuse_common.h index 7c2e86f..bb73d9f 100644 --- a/include/fuse_common.h +++ b/include/fuse_common.h @@ -106,7 +106,9 @@ struct fuse_file_info { #define FUSE_CAP_POSIX_LOCKS (1 << 1) /** - * Indicates that the filesystem supports the O_TRUNC open flag + * Indicates that the filesystem supports the O_TRUNC open flag. If + * disabled, and an application specifies O_TRUNC, fuse first calls + * truncate() and then open() with O_TRUNC filtered out. * * This feature is enabled by default when supported by the kernel. */ diff --git a/include/fuse_lowlevel.h b/include/fuse_lowlevel.h index 835b420..987b24d 100644 --- a/include/fuse_lowlevel.h +++ b/include/fuse_lowlevel.h @@ -439,14 +439,8 @@ struct fuse_lowlevel_ops { /** * Open a file * - * Open flags are available in fi->flags. Creation (O_CREAT, - * O_EXCL, O_NOCTTY) and by default also truncation (O_TRUNC) - * flags will be filtered out. If an application specifies - * O_TRUNC, fuse first calls truncate() and then open(). - * - * If filesystem is able to handle O_TRUNC directly, the - * init() handler should set the `FUSE_CAP_ATOMIC_O_TRUNC` bit - * in ``conn->want``. + * Open flags are available in fi->flags. Creation (O_CREAT, + * O_EXCL, O_NOCTTY) flags will be filtered out. * * Filesystem may store an arbitrary file handle (pointer, * index, etc) in fi->fh, and use this in other all other file -- cgit v1.2.3