aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog.rst
Commit message (Collapse)AuthorAge
...
* Document that -o auto_unmount implies -o nodev,nosuidGravatar Nikolaus Rath2017-03-16
| | | | See also issue #148.
* Added experimental support for building with Meson+NinjaGravatar Nikolaus Rath2017-01-12
|
* Added documentation and test case for null exampleGravatar Nikolaus Rath2016-12-23
|
* Released 3.0.0Gravatar Nikolaus Rath2016-12-09
|
* Released 3.0.0rc3Gravatar Nikolaus Rath2016-11-29
|
* Return signal value if session loop is terminated by signal and improve ↵Gravatar Nikolaus Rath2016-11-29
| | | | documentation
* Make handling of -oallow_root easier to understandGravatar Nikolaus Rath2016-11-22
| | | | | | -oallow_root is handled in userspace, and requires passing -oallow_other to the kernel. This patch should make the code easier to understand and avoid the confusion that gave rise to issue #86.
* 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.
* Enable more capabilities by default, and document defaults.Gravatar Nikolaus Rath2016-11-16
| | | | Fixes #112.
* Update ChangeLog to include recent documentation improvementsGravatar Nikolaus Rath2016-11-16
|
* Abort if fs requests capabilities not supported by kernel.Gravatar Nikolaus Rath2016-11-16
| | | | See also issue #114.
* Add support for more detailed error codes from main loopGravatar Nikolaus Rath2016-11-16
|
* Added documentation for FUSE_CAP_FLOCK_LOCKSGravatar Nikolaus Rath2016-11-10
| | | | Fixes #106.
* Make test for util-linux version more robustGravatar Nikolaus Rath2016-11-10
| | | | | | | The current version fails on Amazon Linux. This check should work better. Fixes #64.
* Don't expect EACCESS errors as rootGravatar Nikolaus Rath2016-11-10
| | | | Fixes #111.
* Released 3.0.0-rc2Gravatar Nikolaus Rath2016-11-06
|
* Fix documentation: fuse_file_info may be NULL for open filesGravatar Nikolaus Rath2016-11-06
| | | | This turns issue #62 from a bug into an enhancement :-).
* Renamed fusermount / mount.fuse to fusermount3 / mount.fuse3Gravatar Nikolaus Rath2016-10-28
|
* Released 3.0.0rc1Gravatar Nikolaus Rath2016-10-28
|
* 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.
* fuse_session_new(): don't accept empty argv, check argv[0]Gravatar Nikolaus Rath2016-10-24
| | | | | | | This should help avoid people to accidentally put options into argv[0]. Fixes #100.
* Turn fuse_operations.nopath_flag into fuse_config.nullpath_okGravatar Nikolaus Rath2016-10-20
| | | | | | 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.
* Pass struct fuse_config to high-level init() handler.Gravatar Nikolaus Rath2016-10-20
|
* ChangeLog: Remind people of to use FUSE_CAP_EXPORT_SUPPORTGravatar Nikolaus Rath2016-10-20
|
* Spelling fixGravatar Nikolaus Rath2016-10-17
| | | | Thanks to (Github user) mtheall for the review!
* Make --help output more suitable for end-userGravatar Nikolaus Rath2016-10-15
| | | | | | | 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.
* Removed -o nopath - it never did anythingGravatar Nikolaus Rath2016-10-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We are overriding this setting with the flag in struct fuse_operations: $ example/hello -f -d ~/tmp/mnt FUSE library version: 3.0.0pre0 nopath: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.25 flags=0x0007fffb max_readahead=0x00020000 INIT: 7.23 flags=0x00006031 max_readahead=0x00020000 max_write=0x00020000 max_background=0 congestion_threshold=0 time_gran=0 unique: 1, success, outsize: 80 $ example/hello -f -d ~/tmp/mnt -o nopath FUSE library version: 3.0.0pre0 nopath: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.25 flags=0x0007fffb max_readahead=0x00020000 INIT: 7.23 flags=0x00006031 max_readahead=0x00020000 max_write=0x00020000 max_background=0 congestion_threshold=0 time_gran=0 unique: 1, success, outsize: 80
* Removed -o nonempty optionGravatar Nikolaus Rath2016-10-15
| | | | | This brings the default behavior in-line with that of the regular `mount` command.
* Drop -o large_read mount optionGravatar Nikolaus Rath2016-10-15
| | | | This was only relevant for 2.4 kernels. Fixes #92.
* Pass fuse_file_info to getattr, chown, chmod, truncate, utimens handlersGravatar Nikolaus Rath2016-10-15
| | | | | | This obsoletes the ftruncate & fgetattr handlers. Fixes #58.
* 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.
* Added lost ChangeLog entries for -o writeback_cache and -o async_dio.Gravatar Nikolaus Rath2016-10-13
|
* Make -o clone_fd into a parameter of session_loop_mt().Gravatar Nikolaus Rath2016-10-13
| | | | | | 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.
* Activate splice_read by default if write_buf is implemented.Gravatar Nikolaus Rath2016-10-13
|
* 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`.
* Added ChangeLog entry for commit 225c12aebf2d2f27e1d0.Gravatar Nikolaus Rath2016-10-09
|
* Renamed cuses example and added test programGravatar Nikolaus Rath2016-10-09
| | | | | | | | An earlier version of the fioclient.c example was intended to be used together with cusexmp.c. The former has since evolved into ioctl_client.c and no longer has the function necessary to test CUSE. Therefore, we've added a new cuse_client.c that is clearly associated with the cuse.c example file system.
* Renamed timefsN examples to fuse_notify_*Gravatar Nikolaus Rath2016-10-09
| | | | | This should make it more obvious at first glance what the different examples do.
* Dropped example/null.cGravatar Nikolaus Rath2016-10-09
| | | | | This does not seem to be working. Maybe because it tries to treat the mountpoint as a file rather than a directory?
* Added timefs3 to test notify_inval_entry.Gravatar Nikolaus Rath2016-10-08
| | | | Fixes #32.
* testfs2: Also test fuse_notify_retrieve().Gravatar Nikolaus Rath2016-10-08
|
* Added timefs[12] examples.Gravatar Nikolaus Rath2016-10-08
| | | | | These examplesdemonstrate the use of the `fuse_lowlevel_notify_store` and `fuse_lowlevel_notify_inval_inode` functions.
* 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.
* Released 3.0.0pre0Gravatar Nikolaus Rath2016-10-03
|
* Added fuse_session_fd()Gravatar Nikolaus Rath2016-10-02
| | | | Fixes #59.
* 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-17 05:10:49 +0000