aboutsummaryrefslogtreecommitdiff
path: root/include/fuse_common.h
Commit message (Collapse)AuthorAge
* Spelling (#223)Gravatar Josh Soref2017-11-27
| | | Fix spelling errors
* Add idle_threads mount option.Gravatar Joseph Dodge2017-08-24
|
* Added public fuse_lib_help(), bumped minor versionGravatar Nikolaus Rath2017-07-08
|
* Fixed description of struct fuse_conn_info->time_granGravatar Nikolaus Rath2017-07-08
| | | | | At least on Linux kernel 4.9, a value of zero gives more than 1-sec accuracy.
* Clarify *_timeout semanticsGravatar Nikolaus Rath2017-06-08
| | | | | When changes always come through kernel, timeouts should be large.
* open(): fix documentation of O_TRUNC flagGravatar Nikolaus Rath2017-03-15
| | | | | The FUSE_CAP_ATOMIC_IO_TRUNC capability is enabled by default, but we didn't update the open() documentation accordingly.
* Return signal value if session loop is terminated by signal and improve ↵Gravatar Nikolaus Rath2016-11-29
| | | | documentation
* Improve documentation of `fuse_file_info.keep_cache`Gravatar Nikolaus Rath2016-11-29
|
* Document that FUSE_CAP_POSIX_ACL turns on -o default_permissionsGravatar Nikolaus Rath2016-11-22
|
* Add support for FUSE_HANDLE_KILLPRIVGravatar Nikolaus Rath2016-11-22
| | | | Fixes #116.
* Add support for FUSE_POSIX_ACLGravatar Nikolaus Rath2016-11-22
| | | | Fixes #117.
* Added support for FUSE_PARALLEL_DIROPSGravatar Nikolaus Rath2016-11-22
| | | | | | Enabled by default since we haven't released libfuse 3.0 yet :-). Fixes #112.
* Document fuse_conn_info.max_backgroundGravatar Nikolaus Rath2016-11-22
| | | | Fixes #95.
* Enable more capabilities by default, and document defaults.Gravatar Nikolaus Rath2016-11-16
| | | | Fixes #112.
* Document "congestion_threshold" parameter.Gravatar Nikolaus Rath2016-11-16
| | | | | | Fixes #96. Thanks to Maxim Patlasov <mpatlasov@virtuozzo.com> for help!
* Make max_background and congestion_threshold "officially undocumented"Gravatar Nikolaus Rath2016-11-14
|
* Improve documentation of FUSE_CAP_AUTO_INVAL_DATAGravatar Nikolaus Rath2016-11-14
| | | | Fixes #84.
* Improve description of FUSE_CAP_NO_OPEN_SUPPORT flag.Gravatar Nikolaus Rath2016-11-14
| | | | Fixes #107.
* Added documentation for FUSE_CAP_FLOCK_LOCKSGravatar Nikolaus Rath2016-11-10
| | | | Fixes #106.
* Improve documentation of fuse_conn_info.time_gran.Gravatar Nikolaus Rath2016-11-10
| | | | Fixes #97.
* Clean-up doxygen documentationGravatar Nikolaus Rath2016-10-28
| | | | Fixes: #81.
* Add max_read to fuse_conn_infoGravatar Nikolaus Rath2016-10-27
| | | | | | | | | | Eventually, this setting should be negotiated in the filesystem's init() handler (like e.g. max_write). However, this requires corresponding changes in the FUSE kernel module. In preparation for this (and to allow a transition period) we already allow (and require) filesystems to set the value in the init() handler in addition to the mount option. The end-goal is tracked in issue #91.
* Removed some more "Changed in version x.py" comments.Gravatar Nikolaus Rath2016-10-27
|
* Improve documentation of capability flags.Gravatar Nikolaus Rath2016-10-27
|
* Removed all "Introduced in..." commentsGravatar Nikolaus Rath2016-10-20
| | | | | Since FUSE 3 is breaking backwards compatibility, this really does not matter.
* Unify handling of fuse_conn_info optionsGravatar Nikolaus Rath2016-10-15
| | | | | | Instead of using command line options to modify struct fuse_conn_info before and after calling the init() handler, we now give the file system explicit control over this.
* do_init(): treat command line options consistentlyGravatar Nikolaus Rath2016-10-13
| | | | | | | Previously, some command line options would change the FUSE defaults but leave the final value to the file systems `init` handler while others would override any changes made by `init`. Now, command line options do both: they modify the default, *and* take precedence.
* Removed 'async_read' field in fuse_conn_infoGravatar Nikolaus Rath2016-10-10
| | | | This is redundant with the capability flags in `wants` and `capable`.
* Removed ``-o big_writes`` optionGravatar Nikolaus Rath2016-10-08
| | | | | | This option is obsolete and should always be enabled. File systems that want to limit the size of write requests should use the ``-o max_write=<N>`` option instead.
* Don't handle --help and --version in fuse_session_new().Gravatar Nikolaus Rath2016-10-02
| | | | | | | | | | | | | | | | | | | Help and version messages can be generated using the new fuse_lowlevel_help(), fuse_lowlevel_version(), fuse_mount_help(), and fuse_mount_version() functions. The fuse_parse_cmdline() function has been made more powerful to do this automatically, and is now explicitly intended only for low-level API users. This is a code simplication patch. We don't have to parse for --help and --version in quite as many places, and we no longer have a low-level initialization function be responsible for the (super-high level) task of printing a program usage message. In the high-level API, we can now handle the command line parsing earlier and avoid running other initialization code if we're just going to abort later on.
* Turn struct fuse_chan into an implementation detailGravatar Nikolaus Rath2016-10-02
| | | | | | | | | | | | | | | | | | | | | The only struct fuse_chan that's accessible to the user application is the "master" channel that is returned by fuse_mount and stored in struct fuse_session. When using the multi-threaded main loop with the "clone_fd" option, each worker thread gets its own struct fuse_chan. However, none of these are available to the user application, nor do they hold references to struct fuse_session (the pointer is always null). Therefore, any presence of struct fuse_chan can be removed without loss of functionality by relying on struct fuse_session instead. This reduces the number of API functions and removes a potential source of confusion (since the new API no longer looks as if it might be possible to add multiple channels to one session, or to share one channel between multiple sessions). Fixes issue #17.
* Introduce separate mount/umount functions for low-level API.Gravatar Nikolaus Rath2016-10-02
|
* Improve documentation of argument parsing.Gravatar Nikolaus Rath2016-10-01
|
* Fixup commit 482a49c.Gravatar Nikolaus Rath2016-04-27
|
* Merge remote-tracking branch 'origin/master'Gravatar Nikolaus Rath2016-04-27
|\
| * Remove leading _ on header guards to comply with reserved identifier ↵Gravatar Sam Stuewe2016-04-23
| | | | | | | | | | requirements (#29) Remove leading _ on header guards to comply with reserved identifier requirements
* | Whitespace cleanup.Gravatar Nikolaus Rath2016-03-29
|/ | | | | | Applied (whitespace-cleanup) to each file. Having whitespace changes in the VCS is ugly, but it ensures that in the future committers can run this function to *avoid* commiting any whitespace.
* Added fuse_pkgversion functionGravatar Christopher Harrison2015-07-30
| | | | Returns the full PACKAGE_VERSION string, per autoconf
* libfuse: add FUSE_CAP_NO_OPEN_SUPPORT flag to ->init()Gravatar Miklos Szeredi2015-04-23
|
* libfuse: add "time_gran" optionGravatar Miklos Szeredi2014-07-15
| | | | | | This allows the filesystem to specify the time granularity it supports when the kernel is responsible for updating times ("writeback_cache" option).
* libfuse: Add "async_dio" and "writeback_cache" optionsGravatar Miklos Szeredi2014-01-29
| | | | | Asynchronous direct I/O is supported by linux kernels 3.13 and later, writeback caching is supported by 3.14 and later.
* libfuse: clean up struct fuse_file_infoGravatar Miklos Szeredi2013-07-18
| | | | | | Remove 'fh_old' which was an ABI compatibility field for a long time. Make 'writepage' a bitfield.
* Documentation fixesGravatar Miklos Szeredi2013-07-17
|
* - added a doxygen main pageGravatar Joachim Schiele2013-06-20
| | | | | | - modified all examples to be included in doxygen - modified the API documentation to have more details - added the 490px_FUSE_structure.svg.png (c) wikipedia
* libfuse: don't force -D_FILE_OFFSET_BITS=64 in pkgconfig file.Gravatar Richard W.M. Jones2013-02-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FUSE_CFLAGS defines -D_FILE_OFFSET_BITS=64. There are three problems with this: (1) A larger program using libfuse might have modules compiled with and without FUSE_CFLAGS, which, if LFS is not enabled and the platform is 32 bit, would result in a fatal mix of 32 and 64 bit off_t. (This would, of course, be a bug, but I think there is a better way to detect this -- see below) (2) Programs may need to be adjusted to support LFS. It's the intention of the LFS standard that the _programmer_ enables LFS once the program has been checked/adjusted. (3) _FILE_OFFSET_BITS does not need to be defined at all on 64 bit Linux. 64 bit off_t is the default there. So I think it's better not to force -D_FILE_OFFSET_BITS=64, and because of (3) I also think you shouldn't test for it. However off_t must still be 64 bits, so how to enforce that? C1X will define static assertions[1], and these can be used to check the size of off_t. Not all compilers support static assertions yet, although several do. Therefore I have surrounded the static assertion with a conservative check that the compiler is GCC >= 4.6. In the long run, this test can be removed and you can just use 'static_assert'.
* libfuse: allow disabling adaptive readdirplusGravatar Eric Wong2013-02-07
| | | | | | | | | | | This switches the -o no_readdirplus option to a tristate string: -o readdirplus=(yes|no|auto) Telling the kernel to always use readdirplus is beneficial to filesystems (e.g. GlusterFS) where the cost to perform readdir and readdirplus are identical. The default remains "auto" (if supported).
* libfuse: add poll_events to fuse_file_infoGravatar Enke Chen2013-02-07
| | | | | Make requested poll events available to the filesystem. If the requested eventsare not available, then this field is zero.
* libfuse: add readdirplus support in fuse_lowlevel_opsGravatar Feng Shuo2013-02-07
| | | | | | | | | | | | | | | | | This patch implements readdirplus support in FUSE usersapce. It adds a new fuse lowlevel operations fuse_lowleve_ops::readdir_plus, corespoding mount options and helper functions to maintain buffer. [From: Eric Wong <normalperson@yhbt.net>] This makes our terminology consistent with NFS and our kernel module, as well as reducing user/developer confusion in the command-line. Note: I'm keeping "fuse_add_direntry_plus" since that is less standardized in its use than "readdirplus" for now. Signed-off-by: Feng Shuo <steve.shuo.feng@gmail.com>
* libfuse: Add '[no_]auto_inval_data' mount optionGravatar Feng Shuo2013-02-06
| | | | | | | | | | | Several caching logic changes have been made on the kernel side to better support network-based fuse filesystems. These include kernel side mtime checking and read path cache revalidation. The new caching logic is enabled through the FUSE_AUTO_INVAL_DATA init flag. Export this to the user via the '[no_]auto_inval_data' mount option. Signed-off-by: Feng Shuo <steve.shuo.feng@gmail.com>
* Start of 3.0 seriesGravatar Miklos Szeredi2012-07-19
| | | | | | | Change the version numbers. This is going to be a new major version of the library breaking backward compatibility on the binary level as well as the source level.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-19 16:30:05 +0000