aboutsummaryrefslogtreecommitdiff
path: root/lib/fuse_lowlevel.c
Commit message (Collapse)AuthorAge
* 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.
* Use "se" instead of "f" for struct fuse_sessionGravatar Nikolaus Rath2016-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fuse_session pointer is sometimes called f and at other times se. The former is an artifact from the time when there still was a separate struct fuse_ll object. For consistency and to easy maintenance, this patch changes the name of the fuse_session pointer to "se" wherever possible. This patch was generated by the following Coccinelle script: @@ symbol f, se; @@ struct fuse_session * -f +se ; <... -f +se ...> @@ expression expr; @@ struct fuse_session * -f +se = expr; <... -f +se ...> @@ identifier fn; @@ fn(...,struct fuse_session * -f +se ,...) { <... -f +se ...> } Due to its complexity, the do_init() function had to be commented out and then patched manually.
* 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.
* Do not close stdout on fuse_session_destroy()Gravatar Consus2016-10-20
| | | | | | | If fuse_session_mount() fails (or was never called in the first place) we end up with the default fd value which happens to be 0. It hurts long-running processes, which lifetime extends beyond session's lifetime.
* fuse_session_new(): accept --debugGravatar Nikolaus Rath2016-10-17
| | | | | | Fixes commit 3e022acf4076. Thanks to Github user mtheall for the review!
* Inlined fuse_mount_help() into fuse_lowlevel_help().Gravatar Nikolaus Rath2016-10-16
| | | | | | | | | Both the BSD and Linux implementation actually accept mostly the same FUSE-specific mount options. Up to now, the BSD help function appended the output of ``mount_fusefs --help``, but looking at http://www.unix.com/man-page/freebsd/8/mount_fusefs/ this is likely more confusing than helpful (since the user is not actually invoking mount_fusefs directly, most of the options don't make sense).
* fuse_session_new: accept -o debug as synonym for -dGravatar Nikolaus Rath2016-10-16
|
* 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.
* 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.
* Merge branch 'fixup-lock-options'Gravatar Nikolaus Rath2016-10-15
|\
| * Re-activated lost no_remote_*lock options.Gravatar Nikolaus Rath2016-10-15
| |
* | 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.
* | Move session options into sub-structGravatar Nikolaus Rath2016-10-13
| | | | | | | | | | | | | | The session options are used only once to determine the proper conn->want flags. It is nice to have them clearly separated from the other struct fuse_session members that are used throughout the life of the file system.
* | Use NULL for option processing function where possible.Gravatar Nikolaus Rath2016-10-13
| |
* | 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.
* Factored out LL_OPTIONS macroGravatar Nikolaus Rath2016-10-10
|
* Removed 'async_read' field in fuse_conn_infoGravatar Nikolaus Rath2016-10-10
| | | | This is redundant with the capability flags in `wants` and `capable`.
* Make several -o NN options work againGravatar Nikolaus Rath2016-10-10
| | | | | In commit 2ed7af, we accidentally set the default values *after* parsing the command line arguments.
* Use "se" instead of "f" for fuse_session pointer where possible.Gravatar Nikolaus Rath2016-10-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | These changes were generated with the following Coccinelle semantic patch: @@ symbol f, se; // avoid unneeded warnings from Coccinelle @@ struct fuse_session * -f +se ; <... -f +se ...> @@ identifier fn; @@ fn(...,struct fuse_session * -f +se ,...) { <... -f +se ...> }
* Fix valgrind warningGravatar Nikolaus Rath2016-10-09
| | | | | If we don't assign a value to padding, we get a warning about reading uninitialized data when sending the iovec to the kernel.
* 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.
* Remove pointless aliasing of fuse_session *se to *fGravatar Nikolaus Rath2016-10-05
| | | | This is an overlooked artifact of the fuse_ll-fuse_session merge.
* Merge fuse_ll into fuse_session (part 8)Gravatar Nikolaus Rath2016-10-04
| | | | Replaced "req->se" with "f" where the latter is already defined.
* Merge fuse_ll into fuse_session (part 7)Gravatar Nikolaus Rath2016-10-04
| | | | | Remove pointless aliasing of "struct fuse_session *se" to "struct fuse_session *f".
* Merge fuse_ll into fuse_session (part 5)Gravatar Nikolaus Rath2016-10-04
| | | | Fixup fuse_session_new().
* Merge fuse_ll into fuse_session (part 4)Gravatar Nikolaus Rath2016-10-04
| | | | Merge fuse_ll_destroy() and fuse_session_destroy().
* Merge fuse_ll into fuse_session (part 3)Gravatar Nikolaus Rath2016-10-04
| | | | Replace se->f with se.
* Merge fuse_ll into fuse_session (part 2)Gravatar Nikolaus Rath2016-10-04
| | | | Replaced all references to req->f with req->se.
* Merge fuse_ll into fuse_session (part 1)Gravatar Nikolaus Rath2016-10-04
| | | | | Merged the structures, and replaced fuse_ll with fuse_session in all type definitions.
* Merge master fuse_chan into fuse_session.Gravatar Nikolaus Rath2016-10-03
| | | | | | | | | | | | | | | | | | This is a code simplification patch. - It confines most of the implementation channel implementation into fuse_loop_mt (which is its only user). - It makes it more obvious in the code that channels are only ever used when using -o clone_fd and multi-threaded main loop. - It simplies the definition of both struct fuse_session and struct fuse_chan. - Theoretically it should result in (minuscule) performance improvements when not using -o clone_fd. - Overall, it removes a lot more lines of source code than it adds :-).
* fuse_lowlevel_notify_poll(): use master channelGravatar Nikolaus Rath2016-10-03
| | | | | | | | | | | | | | | | In theory, a poll handle could hang around much longer than the worker thread that creates it. Furthermore, the thread that created the pollhandle is no more likely to call fuse_lowlevel_notify_poll() than any other thread. In theory, this would have kept the channel alive for much longer than necessary. In practice, there seems to have been a bug that prevented this - and instead allowed the channel to be destroyed while there was still a pollhandle referring to it. Instead of fixing this by calling fuse_chan_get() and fuse_chan_put() in do_poll() and fuse_pollhandle_destroy(), we simply transmit poll notifications over the master channel now.
* Store struct fuse_session* in struct fuse_reqGravatar Nikolaus Rath2016-10-03
|
* Added fuse_session_fd()Gravatar Nikolaus Rath2016-10-02
| | | | Fixes #59.
* Merged fuse_session.c into fuse_lowlevel.cGravatar Nikolaus Rath2016-10-02
| | | | | | This distinction no longer makes sens. fuse_lowlevel.c already contains several session related functions, and fuse_session.c contains various stuff that is more related to the channel interface.
* Extended per-file comments.Gravatar Nikolaus Rath2016-10-02
| | | | | This should make more clear what file contains code for what purpose.
* 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.
* fuse_mount_opts: don't keep max_read= option.Gravatar Nikolaus Rath2016-10-02
| | | | There is no consumer of it down the line.
* Add section headings for --help outputGravatar Nikolaus Rath2016-10-02
| | | | Also, do not include "General options" in usage message.
* 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.
* Renamed fuse_lowlevel_new() to fuse_session_new().Gravatar Nikolaus Rath2016-10-02
|
* Introduce separate mount/umount functions for low-level API.Gravatar Nikolaus Rath2016-10-02
|
* Turned fuse_session_{process,receive}_buf into wrapper functions.Gravatar Nikolaus Rath2016-10-02
|
* Inlined fuse_session_new()Gravatar Nikolaus Rath2016-10-02
| | | | This function is only used in one place.
* Improve documentation of argument parsing.Gravatar Nikolaus Rath2016-10-01
|
* fuse_lowlevel_notify_*: take struct fuse_session instead of struct fuse_chanGravatar Nikolaus Rath2016-09-27
| | | | | | | | | | | 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.
* Inlined calculate_dirent*_size functionsGravatar Nikolaus Rath2016-06-05
|
* Don't use IFTODT macro.Gravatar Nikolaus Rath2016-06-05
| | | | | | | | | IFTODT is provided by libc to convert from mode_t (as included in e.g. struct fstat) to d_type (unsigned char element of struct dirent, as returned by e.g. readdir). However, fuse actually uses a different struct fuse_dirent with a "type" field of type uint32. In other words, the semantics of (struct fuse_dirent).type are not necessarily the same as those of (struct dirent).d_type.
* Inlined fuse_add_direntGravatar Nikolaus Rath2016-06-05
|
* Merge branch 'add-dirent-strlen3' of git://github.com/trapexit/libfuse into ↵Gravatar Nikolaus Rath2016-06-04
|\ | | | | | | trapexit-add-dirent-strlen3
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-28 09:16:15 +0000