aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorLines
2017-09-20Automatically print list of contributors when generating tarballNikolaus Rath-0/+5
2017-09-20Travis CI: Don't use deprecated environmentNikolaus Rath-2/+3
Travis support recommends to install specific pip version to work around problems in new environment.
2017-09-19Correctly define fusermount3 path.Nikolaus Rath-1/+1
2017-09-19Make *_loop_mt() available in version 3.0 againNikolaus Rath-2/+2
The old versions of these symbols were defined with version tag FUSE_3.0, so this is what we have to use in the .symver directive.
2017-09-19Fix versioned symbols in version scriptNikolaus Rath-1/+4
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-19Don't use external symbol names in internal filesNikolaus Rath-7/+6
The fuse_session_loop_mt() and fuse_loop_mt() symbols are only visible when linking against the shared object. The code in lib/, however, is compiled *into* the shared object and should thus use the internal names of these functions. Surprisingly enough, the code still worked before - but only when link time optimization was disabled. Unfortunately, we still can't compile with LTO because it seems that enabling LTO somehow makes the tagged symbols vanish. Without lto, we have: $ nm lib/libfuse3.so | grep fuse_new 0000000000011070 T fuse_new_30 0000000000010a00 t fuse_new_31 0000000000011070 T fuse_new@FUSE_3.0 0000000000010a00 T fuse_new@@FUSE_3.1 and with LTO: $ nm lib/libfuse3.so | grep fuse_new 0000000000019a70 T fuse_new_30 0000000000019270 t fuse_new_31 See also issue #198.
2017-09-17Include source code in documentation.Nikolaus Rath-1/+1
2017-09-17make_release_tarball.sh: be less verboseNikolaus Rath-1/+1
2017-09-17Added some documentation of fuse internals.Nikolaus Rath-0/+17
2017-09-12Released 3.2.0Nikolaus Rath-11/+14
2017-09-12Add script to create release tarball.Nikolaus Rath-0/+28
2017-09-12Use "mkdir" instead of "md" in instructions.Nikolaus Rath-1/+1
Fixes: #205.
2017-09-11fuse_kern_unmount(): close fd before calling umountNikolaus Rath-1/+1
This is what the Linux version does, and it fixes a timeout under FreeBSD when the kernel sends a FUSE_DESTROY request that is never answered.
2017-08-25example/ioctl: build on FreeBSD, but add protocol check instead.Nikolaus Rath-5/+7
2017-08-25do_init(): print missing capabilities if there are any.Nikolaus Rath-1/+2
2017-08-25Fix writeback capability check.Nikolaus Rath-1/+1
2017-08-25examples/{ioctl,null}: don't build under FreeBSD instead of skipping tests.Nikolaus Rath-26/+23
2017-08-24printcap: use temporary directory, not fileNikolaus Rath-6/+3
Mounting a file doesn't seem to work under FreeBSD.
2017-08-24Skip testing null and ioctl examples under FreeBSD.Nikolaus Rath-0/+10
This seems to be unsupported. However, me may also be doing it wrong. I've asked on the freebsd-fs list for help.
2017-08-24Removed unused import.Nikolaus Rath-1/+1
2017-08-24passthrough_ll: only active EXPORT_SUPPORT of supported by kernel.Nikolaus Rath-1/+3
2017-08-24Don't use -o auto_unmount under FreeBSD.Nikolaus Rath-0/+4
2017-08-24Dropped support for building with autotoolsNikolaus Rath-360/+3
It's just too much pain to keep it working.
2017-08-24Use printcap() to control test executionNikolaus Rath-15/+54
That way, we run only tests that are supported by the running kernel.
2017-08-24Added testcase for examples/printcapNikolaus Rath-0/+6
2017-08-24Add idle_threads mount option.Joseph Dodge-21/+105
2017-08-24Renamed notify_inval_inode_fh to invalidate_pathNikolaus Rath-6/+6
The previous name didn't make much sense.
2017-08-24Allow inode cache invalidation in high-level APISławek Rudnicki-4/+379
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-23Added examples/printcapNikolaus Rath-2/+135
2017-08-23fuse_loop_mt(): on error, return errno rather than -1.Nikolaus Rath-2/+5
2017-08-23fuse_loop(): don't return non-zero if there was no errorNikolaus Rath-0/+7
2017-08-22Document and unify error codes of fuse_lowlevel_notify_*Nikolaus Rath-15/+46
2017-08-22Make passthrough_fh work under FreeBSD.Nikolaus Rath-0/+15
2017-08-22Fix two compiler warnings.Nikolaus Rath-2/+2
2017-08-22Document meaning of zero telldir() offset.Nikolaus Rath-15/+16
2017-08-22Allow building without iconv.Nikolaus Rath-1/+9
cfg.has('HAVE_ICONV') was always true.
2017-08-22Use 'buildtype' to set debug/optimization optionsNikolaus Rath-2/+2
Until now, running `mesonconf -D buildtype=debug` didn't have any effect - which was confusing.
2017-08-14directly call fuse_new_31() instead of fuse_new() internallyuserwithuid-3/+6
this fixes building with lto, which failed since commit 503e32d01e4db00e90d7acfd81ab05386559069f
2017-08-14Fixed udev rules directory.Nikolaus Rath-2/+4
2017-08-11Skip tests that aren't supported under FreeBSD.Nikolaus Rath-8/+25
2017-08-11fuse_lib_init(): don't set FUSE_CAP_EXPORT_SUPPORT unconditionallyNikolaus Rath-1/+2
FreeBSD kernel does not support this.
2017-08-11Don't attempt to run fusermount3 under BSD.Nikolaus Rath-10/+21
2017-08-11Call cp with -p instead of --preserve=modeNikolaus Rath-1/+1
Preserving other attributes doesn't hurt, and --preserve is not supported under FreeBSD.
2017-08-11Don't pass --update to cpNikolaus Rath-1/+3
Doesn't work on FreeBSD, and not strictly necessary.
2017-08-11Don't build passthrough_ll under BSD.Nikolaus Rath-2/+10
2017-08-11fuse_kern_unmount(): fix variable type.Nikolaus Rath-1/+2
2017-08-11Fix unused variable warnings under FreeBSD.Nikolaus Rath-2/+2
2017-08-08Fix FreeBSD platform detection.Nikolaus Rath-1/+1
2017-08-07Fix support for FUSE_POSIX_ACLMarcin Sulikowski-0/+9
The kernel may set the FUSE_POSIX_ACL flag in the FUSE_INIT request to notify the userspace daemon that the OS does support POSIX ACLs for FUSE file systems. If the filesystem implementation wants to enable POSIX ACLs, it has to reply with the FUSE_POSIX_ACL flag set. However, the reply to the kernel never includes this flag, even if the implementation expresses the need by setting the FUSE_CAP_POSIX_ACL flag in the fuse_conn_info::want variable passed to its init callback. We modify the library to handle requests for FUSE_CAP_POSIX_ACL correctly, i.e., set the FUSE_POSIX_ACL flag in the FUSE_INIT reply to the kernel. Signed-off-by: Marcin Sulikowski <marcin.sulikowski@editshare.com>
2017-08-06Released 3.1.1Nikolaus Rath-6/+11
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-14 04:58:34 +0000