mirrors/libfuse
0
0
Fork 0
mirror of https://github.com/libfuse/libfuse.git synced 2024-11-23 12:14:15 +08:00
Code Issues Packages Projects Releases Wiki Activity
66a03d4e4b
libfuse/lib/fuse_versionscript

209 lines
3.9 KiB
Plaintext
Raw Normal View History

Remove old symbol versions
2012-07-20 00:47:51 +08:00
FUSE_3.0 {
backward compatibility
2004-12-04 08:40:50 +08:00
global:
fuse_destroy;
fuse_exit;
fuse_loop;
fuse_loop_mt;
cleanup
2005-08-15 07:00:27 +08:00
fuse_reply_attr;
fuse_reply_buf;
fuse_reply_entry;
inode based API first working version
2005-07-13 22:08:19 +08:00
fuse_reply_err;
fuse_reply_none;
cleanup
2005-08-15 07:00:27 +08:00
fuse_reply_readlink;
fuse_reply_write;
inode based API first working version
2005-07-13 22:08:19 +08:00
fuse_reply_xattr;
cleanup
2005-08-15 07:00:27 +08:00
fuse_req_userdata;
fuse_session_destroy;
fuse_session_exit;
fuse_session_exited;
fuse_session_loop;
fuse_session_loop_mt;
fuse_session_reset;
Added fuse_session_fd() Fixes #59.
2016-10-03 12:48:47 +08:00
fuse_session_fd;
added option parsing
2005-12-10 01:41:42 +08:00
fuse_opt_parse;
fuse_opt_add_opt;
fuse_opt_add_arg;
fuse_opt_free_args;
fuse_opt_match;
fix
2006-01-07 02:29:40 +08:00
fuse_parse_cmdline;
fuse_remove_signal_handlers;
fix
2005-11-07 23:30:48 +08:00
fuse_reply_create;
fix
2005-11-12 05:32:42 +08:00
fuse_reply_open;
fuse_reply_statfs;
fix
2006-01-07 02:29:40 +08:00
fuse_set_signal_handlers;
fix
2006-02-17 23:49:25 +08:00
fuse_add_direntry;
libfuse: add readdirplus support in fuse_lowlevel_ops 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>
2013-01-04 16:23:31 +08:00
fuse_add_direntry_plus;
fix
2006-03-17 23:05:40 +08:00
fuse_daemonize;
fuse_get_session;
interrupt support
2006-09-07 14:02:44 +08:00
fuse_interrupted;
Renamed fuse_lowlevel_new() to fuse_session_new().
2016-10-03 01:44:16 +08:00
fuse_session_new;
fix
2006-01-20 23:15:21 +08:00
fuse_main_real;
fix
2006-03-17 23:05:40 +08:00
fuse_mount;
Support application-defined I/O functions for FUSE fd The io for FUSE requests and responses can now be further customized by allowing to write custom functions for reading/writing the responses. This includes overriding the splice io. The reason for this addition is that having a custom file descriptor is not sufficient to allow custom io. Different types of file descriptor require different mechanisms of io interaction. For example, some file descriptor communication has boundaries (SOCK_DGRAM, EOF, etc...), while other types of fd:s might be unbounded (SOCK_STREAMS, ...). For unbounded communication, you have to read the header of the FUSE request first, and then read the remaining packet data. Furthermore, the one read call does not necessarily return all the data expected, requiring further calls in a loop.
2023-01-10 18:04:35 +08:00
fuse_session_custom_io;
Introduce separate mount/umount functions for low-level API.
2016-10-03 01:26:40 +08:00
fuse_session_mount;
fix
2006-01-20 23:15:21 +08:00
fuse_new;
revert to version 2.6
2006-01-24 01:11:24 +08:00
fuse_opt_insert_arg;
interrupt support
2006-09-07 14:02:44 +08:00
fuse_reply_lock;
fuse_req_interrupt_func;
fuse_req_interrupted;
pass device file descriptor to fuse_unmount
2006-03-01 17:40:35 +08:00
fuse_unmount;
Introduce separate mount/umount functions for low-level API.
2016-10-03 01:26:40 +08:00
fuse_session_unmount;
Add filesystem stacking support to high level API
2007-02-04 07:32:47 +08:00
fuse_fs_access;
fuse_fs_bmap;
fuse_fs_chmod;
fuse_fs_chown;
fuse_fs_create;
fuse_fs_destroy;
fuse_fs_flush;
fuse_fs_fsync;
fuse_fs_fsyncdir;
fuse_fs_getattr;
fuse_fs_getxattr;
fuse_fs_init;
fuse_fs_link;
fuse_fs_listxattr;
fuse_fs_lock;
fuse_fs_mkdir;
fuse_fs_mknod;
fuse_fs_new;
fuse_fs_open;
fuse_fs_opendir;
fuse_fs_read;
fuse_fs_readdir;
fuse_fs_readlink;
fuse_fs_release;
fuse_fs_releasedir;
fuse_fs_removexattr;
fuse_fs_rename;
fuse_fs_rmdir;
fuse_fs_setxattr;
fuse_fs_statfs;
fuse_fs_symlink;
fuse_fs_truncate;
fuse_fs_unlink;
fuse_fs_utimens;
fuse_fs_write;
Released 2.7.0
2007-07-02 19:29:19 +08:00
fuse_reply_iov;
Add fs subtype support to libfuse and fusermount
2007-06-21 05:37:58 +08:00
fuse_version;
Added missing export of fuse_pkgversion.
2016-10-10 05:43:56 +08:00
fuse_pkgversion;
Add missing fuse_reply_bmap to versionscript. Debian Bug#531329. Reported by Goswin Brederlow
2009-06-18 17:26:22 +08:00
fuse_reply_bmap;
CUSE patches from Tejun Heo
2009-06-18 19:11:54 +08:00
cuse_lowlevel_new;
cuse_lowlevel_main;
cuse_lowlevel_setup;
cuse_lowlevel_teardown;
* Implement ioctl support. On high level interface only "restricted" ioctls are supported (which are defined with the _IO(), _IOR(), _IOW() or _IOWR() macros). Unrestricted ioctls will only be allwed to CUSE (Character Device in Userspace) servers. Patch by Tejun Heo
2008-12-05 18:55:36 +08:00
fuse_fs_ioctl;
* Implement poll support. Patch by Tejun Heo
2008-12-09 03:26:53 +08:00
fuse_fs_poll;
* Add missing fuse_session_data to versionscript * Make sure all global symbols are prefixed with "fuse_" or "cuse_" * Released 2.8.0
2009-08-19 00:13:33 +08:00
fuse_get_context;
fuse_getgroups;
fuse_lowlevel_notify_inval_entry;
fuse_lowlevel_notify_inval_inode;
* Implement poll support. Patch by Tejun Heo
2008-12-09 03:26:53 +08:00
fuse_lowlevel_notify_poll;
fuse_notify_poll;
* Allow commas in options to be escaped with a backslash * Add new function: fuse_opt_add_opt_escaped() * Add missing fuse_reply_bmap() to the version script
2008-10-17 03:11:28 +08:00
fuse_opt_add_opt_escaped;
* Implement poll support. Patch by Tejun Heo
2008-12-09 03:26:53 +08:00
fuse_pollhandle_destroy;
* Implement ioctl support. On high level interface only "restricted" ioctls are supported (which are defined with the _IO(), _IOR(), _IOW() or _IOWR() macros). Unrestricted ioctls will only be allwed to CUSE (Character Device in Userspace) servers. Patch by Tejun Heo
2008-12-05 18:55:36 +08:00
fuse_reply_ioctl;
CUSE patches from Tejun Heo
2009-06-18 19:11:54 +08:00
fuse_reply_ioctl_iov;
* Implement ioctl support. On high level interface only "restricted" ioctls are supported (which are defined with the _IO(), _IOR(), _IOW() or _IOWR() macros). Unrestricted ioctls will only be allwed to CUSE (Character Device in Userspace) servers. Patch by Tejun Heo
2008-12-05 18:55:36 +08:00
fuse_reply_ioctl_retry;
* Implement poll support. Patch by Tejun Heo
2008-12-09 03:26:53 +08:00
fuse_reply_poll;
* The context is extended with a 'umask' field. The umask is sent for mknod, mkdir and create requests by linux kernel version 2.6.31 or later, otherwise the umask is set to zero. Also introduce a new feature flag: FUSE_CAP_DONT_MASK. If the kernel supports this feature, then this flag will be set in conn->capable in the ->init() method. If the filesystem sets this flag in in conn->want, then the create modes will not be masked. * Add low level interfaces for lookup cache and attribute invalidation. This feature is available in linux kernels 2.6.31 or later. Patch by John Muir * Kernel interface version is now 7.12
2009-07-02 20:26:36 +08:00
fuse_req_ctx;
* Add missing fuse_session_data to versionscript * Make sure all global symbols are prefixed with "fuse_" or "cuse_" * Released 2.8.0
2009-08-19 00:13:33 +08:00
fuse_req_getgroups;
libfuse: add buffer interface Add a generic buffer interface for use with I/O. Buffer vectors are supplied and each buffer in the vector may be a memory pointer or a file descriptor. The fuse_reply_fd() interface is converted to using buffers.
2010-07-12 23:17:25 +08:00
fuse_buf_copy;
fuse_buf_size;
add read_buf method to high level API Add a new read_buf() method to the highlevel API. This allows returning a generic buffer from the read method, which in turn allows zero copy reads.
2010-11-10 18:41:21 +08:00
fuse_fs_read_buf;
add write_buf method to high level API Add new write_buf() method to the highlevel API. Similarly to the lowlevel write_buf() method, this allows implementing zero copy writes.
2010-11-10 18:41:21 +08:00
fuse_fs_write_buf;
libfuse: add retrieve request Retrieve data stored in the kernel buffers for a given inode.
2010-11-09 04:13:32 +08:00
fuse_lowlevel_notify_retrieve;
libfuse: add store request Request data to be stored in the kernel buffers for a given inode.
2010-11-09 01:38:23 +08:00
fuse_lowlevel_notify_store;
libfuse: add buffer interface Add a generic buffer interface for use with I/O. Buffer vectors are supplied and each buffer in the vector may be a memory pointer or a file descriptor. The fuse_reply_fd() interface is converted to using buffers.
2010-07-12 23:17:25 +08:00
fuse_reply_data;
libfuse: support zero copy writes in lowlevel interface Add new ->write_buf() method to low level interface. This allows passig a generic buffer, either containing a memory buffer or a file descriptor. This allows implementing zero copy writes. Add fuse_session_receive_buf() and fuse_session_process_buf() which may be used in event loop implementations to replace fuse_chan_recv() and fuse_session_process() respectively.
2010-11-09 00:11:46 +08:00
fuse_session_process_buf;
fuse_session_receive_buf;
add "remember" option This works similar to "noforget" except that eventually the node will be allowed to expire from the cache.
2011-06-02 20:27:02 +08:00
fuse_start_cleanup_thread;
fuse_stop_cleanup_thread;
fuse_clean_cache;
libfuse: Notifying the kernel of deletion. libfuse part to allow a FUSE file-system to tell the kernel when a file or directory is deleted. If the specified dentry has the specified inode number, the kernel will unhash it. Signed-off-by: John Muir <john@jmuir.com> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
2011-12-07 04:56:34 +08:00
fuse_lowlevel_notify_delete;
Add missing fuse_fs_flock to fuse_versionscript
2012-04-20 20:17:39 +08:00
fuse_fs_flock;
Add FALLOCATE operation fallocate filesystem operation preallocates media space for the given file. If fallocate returns success then any subsequent write to the given range never fails with 'not enough space' error.
2012-04-23 09:49:35 +08:00
fuse_fs_fallocate;
Don't handle --help and --version in fuse_session_new(). 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-03 11:52:33 +08:00
fuse_lowlevel_help;
fuse_lowlevel_version;
fuse_parse_cmdline(): do not print help/version text The current behavior makes it difficult to add help for additional options. With the change, this becomes a lot easier.
2016-10-10 08:08:29 +08:00
fuse_cmdline_help;
Update linker script - Fixes commit d49f2e77b4. - Fixes commit 199fc0f833. - Thanks to Github user mtheall for the review!
2016-10-18 11:20:21 +08:00
fuse_apply_conn_info_opts;
fuse_parse_conn_info_opts;
Implement lseek operation (#457)
2019-11-03 17:44:31 +08:00
fuse_fs_lseek;
fuse_reply_lseek;
fix
2006-02-17 23:49:25 +08:00
local:
Add filesystem stacking support to high level API
2007-02-04 07:32:47 +08:00
*;
Remove old symbol versions
2012-07-20 00:47:51 +08:00
};
Tell emacs to use tabs for linkerscript.
2016-10-03 01:10:29 +08:00
Added public fuse_lib_help(), bumped minor version
2017-07-07 21:25:41 +08:00
FUSE_3.1 {
global:
fuse_lib_help;
Allow inode cache invalidation in high-level API We re-introduce the functionality of invalidating the caches for an inode specified by path by adding a new routine fuse_invalidate_path. This is useful for network-based file systems which use the high-level API, enabling them to notify the kernel about external changes. This is a revival of Miklos Szeredi's original code for the fuse_invalidate routine.
2017-08-07 18:41:33 +08:00
fuse_invalidate_path;
Fix versioned symbols in version script According to "How to Write Shared Libraries" by Ulrich Drepper (https://www.akkadia.org/drepper/dsohowto.pdf), the version script should contain the exported name of the versioned symbol once in each tag for which it has been defined by .symver.
2017-09-20 03:26:51 +08:00
fuse_new_30;
Fixes when HAVE_LIBC_VERSIONED_SYMBOLS is not defined fuse_loop_mt and fuse_new had not been defined when HAVE_LIBC_VERSIONED_SYMBOLS had not been set and additionally, fuse_new_31 was missing in the version script and was therefore an unusable symbol. This also adds a test for unset HAVE_LIBC_VERSIONED_SYMBOLS.
2023-01-03 18:46:11 +08:00
fuse_new_31;
Fix versioned symbols in version script According to "How to Write Shared Libraries" by Ulrich Drepper (https://www.akkadia.org/drepper/dsohowto.pdf), the version script should contain the exported name of the versioned symbol once in each tag for which it has been defined by .symver.
2017-09-20 03:26:51 +08:00
fuse_new;
Added public fuse_lib_help(), bumped minor version
2017-07-07 21:25:41 +08:00
} FUSE_3.0;
Add idle_threads mount option.
2017-08-24 20:37:10 +08:00
FUSE_3.2 {
global:
Fix versioned symbols in version script According to "How to Write Shared Libraries" by Ulrich Drepper (https://www.akkadia.org/drepper/dsohowto.pdf), the version script should contain the exported name of the versioned symbol once in each tag for which it has been defined by .symver.
2017-09-20 03:26:51 +08:00
fuse_session_loop_mt;
Add idle_threads mount option.
2017-08-24 20:37:10 +08:00
fuse_session_loop_mt_31;
Define fuse_session_loop_mt as a macro on uclibc and MacOS (#532) On uclibc and MacOS we don't use versioned symbols. Hence, there's no definition for fuse_session_loop_mt on those cases and the linker won't be able to resolve calls to fuse_session_loop_mt() Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
2020-08-09 19:37:26 +08:00
fuse_session_loop_mt_32;
Fix versioned symbols in version script According to "How to Write Shared Libraries" by Ulrich Drepper (https://www.akkadia.org/drepper/dsohowto.pdf), the version script should contain the exported name of the versioned symbol once in each tag for which it has been defined by .symver.
2017-09-20 03:26:51 +08:00
fuse_loop_mt;
Add idle_threads mount option.
2017-08-24 20:37:10 +08:00
fuse_loop_mt_31;
} FUSE_3.1;
Add unprivileged option in `mount.fuse3` The unprivileged option allows to run the FUSE file system process without privileges by dropping capabilities and preventing them from being re-acquired via setuid / fscaps etc. To accomplish this, mount.fuse sets up the `/dev/fuse` file descriptor and mount itself and passes the file descriptor via the `/dev/fd/%u` mountpoint syntax to the FUSE file system.
2018-08-31 15:44:04 +08:00
FUSE_3.3 {
global:
fuse_open_channel;
} FUSE_3.2;
libfuse: add copy_file_range() support Add support for the relatively new copy_file_range() syscall. Backend filesystems can now implement an efficient way of cloning/duplicating data ranges within files. See 'man 2 copy_file_range' for more details.
2018-06-19 01:31:43 +08:00
FUSE_3.4 {
global:
fuse_fs_copy_file_range;
} FUSE_3.3;
log: move fuse_log() to the public header file Applications may wish to call fuse_log() for unified logging. This way they don't need to define their own wrappers to invoke the log message handler function installed by fuse_set_log_func(). Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2019-09-10 18:36:56 +08:00
FUSE_3.7 {
global:
fuse_set_log_func;
fuse_log;
Fixed an issue with the linker version script. (#483) Fixes #467.
2020-01-02 19:06:18 +08:00
} FUSE_3.4;
log: move fuse_log() to the public header file Applications may wish to call fuse_log() for unified logging. This way they don't need to define their own wrappers to invoke the log message handler function installed by fuse_set_log_func(). Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2019-09-10 18:36:56 +08:00
API update for fuse_loop_config additions struct fuse_loop_config was passed as a plain struct, without any version identifer. This had two implications 1) Any addition of new parameters required a FUSE_SYMVER for fuse_session_loop_mt() and fuse_loop_mt() as otherwise a read beyond end-of previous struct size might have happened. 2) Filesystems also might have been recompiled and the developer might not have noticed the struct extensions and unexpected for the developer (or people recomliling the code) uninitialized parameters would have been passed. Code is updated to have struct fuse_loop_config as an opaque/private data type for file systems that want version 312 (FUSE_MAKE_VERSION(3, 12)). The deprecated fuse_loop_config_v1 is visible, but should not be used outside of internal conversion functions File systems that want version >= 32 < 312 get the previous struct (through ifdefs) and the #define of fuse_loop_mt and fuse_session_loop_mt ensures that these recompiled file systems call into the previous API, which then converts the struct. This is similar to existing compiled applications when just libfuse updated, but binaries it is solved with the FUSE_SYMVER ABI compact declarations. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-04-09 04:30:27 +08:00
FUSE_3.12 {
global:
fuse_session_loop_mt;
fuse_session_loop_mt_312;
fuse_loop_mt;
fuse_loop_mt_32;
fuse_loop_mt_312;
fuse_loop_cfg_create;
fuse_loop_cfg_destroy;
fuse_loop_cfg_set_idle_threads;
fuse-loop/fuse_do_work: Avoid lots of thread creations/destructions On benchmarking metadata operations with a single threaded bonnie++ and "max_idle_threads" limited to 1, 'top' was showing suspicious 160% cpu usage. Profiling the system with flame graphs showed that an astonishing amount of CPU time was spent in thread creation and destruction. After verifying the code it turned out that fuse_do_work() was creating a new thread every time all existing idle threads were already busy. And then just a few lines later after processing the current request it noticed that it had created too many threads and destructed the current thread. I.e. there was a thread creation/destruction ping-pong. Code is changed to only create new threads if the max number of threads is not reached. Furthermore, thread destruction is disabled, as creation/destruction is expensive in general. With this change cpu usage of passthrough_hp went from ~160% to ~80% (with different values of max_idle_threads). And bonnie values got approximately faster by 90%. This is a with single threaded bonnie++ bonnie++ -x 4 -q -s0 -d <path> -n 30:1:1:10 -r 0 Without this patch, using the default max_idle_threads=10 and just a single bonnie++ the thread creation/destruction code path is not triggered. Just one libfuse and one application thread is just a corner case - the requirement for the issue was just n-application-threads >= max_idle_threads. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-03-24 19:19:57 +08:00
fuse_loop_cfg_set_max_threads;
API update for fuse_loop_config additions struct fuse_loop_config was passed as a plain struct, without any version identifer. This had two implications 1) Any addition of new parameters required a FUSE_SYMVER for fuse_session_loop_mt() and fuse_loop_mt() as otherwise a read beyond end-of previous struct size might have happened. 2) Filesystems also might have been recompiled and the developer might not have noticed the struct extensions and unexpected for the developer (or people recomliling the code) uninitialized parameters would have been passed. Code is updated to have struct fuse_loop_config as an opaque/private data type for file systems that want version 312 (FUSE_MAKE_VERSION(3, 12)). The deprecated fuse_loop_config_v1 is visible, but should not be used outside of internal conversion functions File systems that want version >= 32 < 312 get the previous struct (through ifdefs) and the #define of fuse_loop_mt and fuse_session_loop_mt ensures that these recompiled file systems call into the previous API, which then converts the struct. This is similar to existing compiled applications when just libfuse updated, but binaries it is solved with the FUSE_SYMVER ABI compact declarations. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-04-09 04:30:27 +08:00
fuse_loop_cfg_set_clone_fd;
fuse_loop_cfg_convert;
fuse-loop/fuse_do_work: Avoid lots of thread creations/destructions On benchmarking metadata operations with a single threaded bonnie++ and "max_idle_threads" limited to 1, 'top' was showing suspicious 160% cpu usage. Profiling the system with flame graphs showed that an astonishing amount of CPU time was spent in thread creation and destruction. After verifying the code it turned out that fuse_do_work() was creating a new thread every time all existing idle threads were already busy. And then just a few lines later after processing the current request it noticed that it had created too many threads and destructed the current thread. I.e. there was a thread creation/destruction ping-pong. Code is changed to only create new threads if the max number of threads is not reached. Furthermore, thread destruction is disabled, as creation/destruction is expensive in general. With this change cpu usage of passthrough_hp went from ~160% to ~80% (with different values of max_idle_threads). And bonnie values got approximately faster by 90%. This is a with single threaded bonnie++ bonnie++ -x 4 -q -s0 -d <path> -n 30:1:1:10 -r 0 Without this patch, using the default max_idle_threads=10 and just a single bonnie++ the thread creation/destruction code path is not triggered. Just one libfuse and one application thread is just a corner case - the requirement for the issue was just n-application-threads >= max_idle_threads. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-03-24 19:19:57 +08:00
fuse_parse_cmdline;
fuse_parse_cmdline_30;
fuse_parse_cmdline_312;
Initial patch provided by Miklos Szeredi <mszeredi@redhat.com>
2022-10-27 23:52:10 +08:00
fuse_lowlevel_notify_expire_entry;
API update for fuse_loop_config additions struct fuse_loop_config was passed as a plain struct, without any version identifer. This had two implications 1) Any addition of new parameters required a FUSE_SYMVER for fuse_session_loop_mt() and fuse_loop_mt() as otherwise a read beyond end-of previous struct size might have happened. 2) Filesystems also might have been recompiled and the developer might not have noticed the struct extensions and unexpected for the developer (or people recomliling the code) uninitialized parameters would have been passed. Code is updated to have struct fuse_loop_config as an opaque/private data type for file systems that want version 312 (FUSE_MAKE_VERSION(3, 12)). The deprecated fuse_loop_config_v1 is visible, but should not be used outside of internal conversion functions File systems that want version >= 32 < 312 get the previous struct (through ifdefs) and the #define of fuse_loop_mt and fuse_session_loop_mt ensures that these recompiled file systems call into the previous API, which then converts the struct. This is similar to existing compiled applications when just libfuse updated, but binaries it is solved with the FUSE_SYMVER ABI compact declarations. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-04-09 04:30:27 +08:00
} FUSE_3.4;
Add in the libfuse version a program was compiled with (#942) The API stays the same, the libfuse version comes from inlined functions, which are defined fuse_lowlevel.h and fuse.h. As these inlined functions are defined in the header files they get added into the application, similar as if these were preprocessor macros. Macro vs inlined function is then just a style issue - I personally prefer the latter. fuse_session_new() -> static inlinei, in the application _fuse_session_new -> inside of libfuse fuse_new() -> static inline, in the application _fuse_new() -> inside of libfuse Note: Entirely untested is the fuse 30 api - we need a test for it. And we do not have any ABI tests at all. Signed-off-by: Bernd Schubert <bernd.schubert@fastmail.fm>
2024-05-13 18:32:06 +08:00
FUSE_3.17 {
global:
_fuse_session_new_317;
_fuse_new;
_fuse_new_30;
_fuse_new_317;
fuse_main_real_317;
Enable passthrough mode for read/write operations (#919) Add support for filesystem passthrough read/write of files. When the FUSE_PASSTHROUGH capability is enabled, the FUSE server may decide, while handling the "open" or "create" requests, if the given file can be accessed by that process in "passthrough" mode, meaning that all the further read and write operations would be forwarded by the kernel directly to the backing file rather than to the FUSE server. All requests other than read or write are still handled by the server. This allows for an improved performance on reads and writes, especially in the case of reads at random offsets, for which no (readahead) caching mechanism would help, reducing the performance gap between FUSE and native filesystem access. Extend also the passthrough_hp example with the new passthrough feature. This example opens a kernel backing file per FUSE inode on the first FUSE file open of that inode and closes the backing file on the release of the last FUSE file on that inode. All opens of the same inode passthrough to the same backing file. A combination of fi->direct_io and fi->passthrough is allowed. It means that read/write operations go directly to the server, but mmap is done on the backing file. This allows to open some fds of the inode in passthrough mode and some fd of the same inode in direct_io/passthrough_mmap mode. Signed-off-by: Alessio Balsini <balsini@android.com> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
2024-05-13 21:30:25 +08:00
fuse_passthrough_open;
fuse_passthrough_close;
Fix compatibility issue around fuse_custom_io->clone_fd (#953) Fixes: 73cd124d0408 ("Add clone_fd to custom IO (#927)") Signed-off-by: Xiaoguang Wang <lege.wang@jaguarmicro.com>
2024-06-02 05:18:35 +08:00
fuse_session_custom_io_30;
fuse_session_custom_io_317;
Add syslog and fatal signal handler feature I see random ENOTCONN failures in xfstest generic/013 and generic/014 in my branch, but earliest on the 2nd run - takes ~12hours to get the issue, but then there are no further information logged. ENOTCONN points to a daemon crash - I need backtraces and a core dump. This adds optional handling of fatal signals to print a core dump and optional syslog logging with these new public functions: fuse_set_fail_signal_handlers() In addition to the existing fuse_set_signal_handlers(). This is not enabled together with fuse_set_signal_handlers(), as it is change in behavior and file systems might already have their own fatal handlers. fuse_log_enable_syslog Print logs to syslog instead of stderr fuse_log_close_syslog Close syslog (for now just does closelog()) Code in fuse_signals.c is also updated, to be an array of signals, and setting signal handlers is now down with a for-loop instead of one hand coded set_one_signal_handler() per signal.
2024-07-11 05:04:46 +08:00
fuse_set_fail_signal_handlers;
fuse_log_enable_syslog;
fuse_log_close_syslog;
Add in the libfuse version a program was compiled with (#942) The API stays the same, the libfuse version comes from inlined functions, which are defined fuse_lowlevel.h and fuse.h. As these inlined functions are defined in the header files they get added into the application, similar as if these were preprocessor macros. Macro vs inlined function is then just a style issue - I personally prefer the latter. fuse_session_new() -> static inlinei, in the application _fuse_session_new -> inside of libfuse fuse_new() -> static inline, in the application _fuse_new() -> inside of libfuse Note: Entirely untested is the fuse 30 api - we need a test for it. And we do not have any ABI tests at all. Signed-off-by: Bernd Schubert <bernd.schubert@fastmail.fm>
2024-05-13 18:32:06 +08:00
} FUSE_3.12;
Tell emacs to use tabs for linkerscript.
2016-10-03 01:10:29 +08:00
# Local Variables:
# indent-tabs-mode: t
# End:
Reference in New Issue Copy Permalink