aboutsummaryrefslogtreecommitdiffstats
path: root/include
AgeCommit message (Collapse)AuthorLines
2016-11-06Fix documentation: fuse_file_info may be NULL for open filesNikolaus Rath-8/+12
This turns issue #62 from a bug into an enhancement :-).
2016-11-06Removed reference to fgetattr and ftruncate (don't exist anymore)Nikolaus Rath-3/+3
2016-11-06Fixed typo in comment.Nikolaus Rath-1/+1
2016-10-28Clean-up doxygen documentationNikolaus Rath-13/+7
Fixes: #81.
2016-10-27Add max_read to fuse_conn_infoNikolaus Rath-0/+14
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.
2016-10-27Removed some more "Changed in version x.py" comments.Nikolaus Rath-20/+0
2016-10-27Recommend when to use -o default_permissions automaticallyNikolaus Rath-6/+12
2016-10-27Improve documentation of capability flags.Nikolaus Rath-18/+83
2016-10-25Clarify difference between notify_inval_entry and notify_delete().Nikolaus Rath-3/+8
Fixes #85.
2016-10-24fuse_session_new(): don't accept empty argv, check argv[0]Nikolaus Rath-5/+19
This should help avoid people to accidentally put options into argv[0]. Fixes #100.
2016-10-20Turn fuse_operations.nopath_flag into fuse_config.nullpath_okNikolaus Rath-25/+13
Modifying struct fuse_config in the init() handler is the canonical way to adjust file-system implementation specific settings. There is no need to have flags in struct fuse_operations.
2016-10-20Pass struct fuse_config to high-level init() handler.Nikolaus Rath-2/+181
2016-10-20Removed all "Introduced in..." commentsNikolaus Rath-72/+7
Since FUSE 3 is breaking backwards compatibility, this really does not matter.
2016-10-16Default to FUSE_USE_VERSION 30Nikolaus Rath-4/+3
2016-10-16fuse_new(): instead of listing options, refer to mount.fuse(8)Nikolaus Rath-25/+6
2016-10-16fuse_session_new(): instead of listing options, refer to mount.fuse(8)Nikolaus Rath-10/+5
2016-10-15Make --help output more suitable for end-userNikolaus Rath-18/+42
We now only list options that are potentially useful for an end-user (and unlikely to accidentally break a file system). The full list of FUSE options has been moved to the documentation of the fuse_new() and fuse_session_new() functions.
2016-10-15Pass fuse_file_info to getattr, chown, chmod, truncate, utimens handlersNikolaus Rath-47/+39
This obsoletes the ftruncate & fgetattr handlers. Fixes #58.
2016-10-15Unify handling of fuse_conn_info optionsNikolaus Rath-10/+61
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.
2016-10-13Make -o clone_fd into a parameter of session_loop_mt().Nikolaus Rath-2/+7
This option really affects the behavior of the session loop, not the low-level interface. Therefore, it does not belong in the fuse_session object.
2016-10-13Mention atomic_o_trunc capability in description of open() handler.Nikolaus Rath-6/+12
2016-10-13do_init(): treat command line options consistentlyNikolaus Rath-3/+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.
2016-10-10Document when fuse_reply_data will use splice()Nikolaus Rath-0/+27
2016-10-10Removed 'async_read' field in fuse_conn_infoNikolaus Rath-5/+0
This is redundant with the capability flags in `wants` and `capable`.
2016-10-10fuse_main(): extend support for printing helpNikolaus Rath-1/+18
There's now a way to inhibit the "usage" line (which actually got lost in commit 225c12aebf2d), which makes it easier for simply file-systems to generate good-looking --help output.
2016-10-09fuse_parse_cmdline(): do not print help/version textNikolaus Rath-15/+14
The current behavior makes it difficult to add help for additional options. With the change, this becomes a lot easier.
2016-10-09Fix documentation of fuse_parse_cmdline().Nikolaus Rath-1/+1
For --help and --version, it returns -1.
2016-10-08Update list of requests that can be answered with fuse_reply_none().Nikolaus Rath-0/+2
2016-10-08Clarify that readdir() *may* report . and .. entries.Nikolaus Rath-0/+3
2016-10-08Removed ``-o big_writes`` optionNikolaus Rath-2/+2
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.
2016-10-03fuse_session_process_buf(): improve documentationNikolaus Rath-3/+4
2016-10-02Added fuse_session_fd()Nikolaus Rath-1/+17
Fixes #59.
2016-10-02Document that client pid/gid/uid may be zero.Nikolaus Rath-2/+9
Fixes #67.
2016-10-02Don't handle --help and --version in fuse_session_new().Nikolaus Rath-31/+62
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.
2016-10-02Edited comments for clarity.Nikolaus Rath-12/+9
2016-10-02Turn struct fuse_chan into an implementation detailNikolaus Rath-109/+34
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.
2016-10-02Renamed fuse_lowlevel_new() to fuse_session_new().Nikolaus Rath-9/+10
2016-10-02Re-order declarations to reflect typical order of useNikolaus Rath-71/+73
2016-10-02Introduce separate mount/umount functions for low-level API.Nikolaus Rath-26/+53
2016-10-01Improve documentation of argument parsing.Nikolaus Rath-3/+27
2016-09-27Documentation improvements.Nikolaus Rath-6/+10
2016-09-27fuse_lowlevel_notify_*: take struct fuse_session instead of struct fuse_chanNikolaus Rath-10/+10
The only struct fuse_chan that's available to the user application is the one that is returned by fuse_mount. However, this is also permanently available from struct fuse_session. A later patch will therefore remove struct fuse_chan from the public API completely. This patch prepares for this by changing the fuse_lowlevel_notify_* functions to take a struct fuse_session parameter instead of a struct fuse_chan parameter.
2016-04-27Fixup commit 482a49c.Nikolaus Rath-1/+1
2016-04-27Merge remote-tracking branch 'origin/master'Nikolaus Rath-17/+17
2016-04-23Remove leading _ on header guards to comply with reserved identifier ↵Sam Stuewe-15/+15
requirements (#29) Remove leading _ on header guards to comply with reserved identifier requirements
2016-04-02Fix spelling mistakeEric Engestrom-1/+1
2016-03-29Whitespace cleanup.Nikolaus Rath-11/+11
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.
2016-03-29Inlined fuse_chan_fdNikolaus Rath-8/+0
2016-03-09fuse.h doc fix: The f_frsize field is not ignored by the statfs operation.Jan Blumschein-1/+1
Apparently f_frsize has been passed on transparently since 2b4781100812d42e704c39c51303cd28ad3f9aa6 (Nov 28, 2005).
2016-01-14Extend write_buf documentationNikolaus Rath-0/+5
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-08 05:01:06 +0000