| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Travis support recommends to install specific pip
version to work around problems in new environment.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: #205.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Mounting a file doesn't seem to work under FreeBSD.
|
|
|
|
|
| |
This seems to be unsupported. However, me may also be
doing it wrong. I've asked on the freebsd-fs list for help.
|
| |
|
| |
|
| |
|
|
|
|
| |
It's just too much pain to keep it working.
|
|
|
|
| |
That way, we run only tests that are supported by the running kernel.
|
| |
|
| |
|
|
|
|
| |
The previous name didn't make much sense.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
cfg.has('HAVE_ICONV') was always true.
|
|
|
|
|
| |
Until now, running `mesonconf -D buildtype=debug` didn't have any
effect - which was confusing.
|
|
|
|
| |
this fixes building with lto, which failed since commit 503e32d01e4db00e90d7acfd81ab05386559069f
|
| |
|
| |
|
|
|
|
| |
FreeBSD kernel does not support this.
|
| |
|
|
|
|
|
| |
Preserving other attributes doesn't hurt, and --preserve
is not supported under FreeBSD.
|
|
|
|
| |
Doesn't work on FreeBSD, and not strictly necessary.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|