| Commit message (Collapse) | Author | Age |
|
|
|
| |
It's just too much pain to keep it working.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
this fixes building with lto, which failed since commit 503e32d01e4db00e90d7acfd81ab05386559069f
|
|
|
|
| |
FreeBSD kernel does not support this.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
This should simplify the code a lot. It also corrects a bug in
that the (former) add_default_fsname() function actually set
the -osubtype option.
|
|
|
|
|
|
| |
mount_bsd.c is only used when compiling for *BSD, and FreeBSD
is the only BSD that supports FUSE. So there really is no need
to check if this file is compiled under FreeBSD.
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Banglang <banglang.huang@foxmail.com>
|
|
|
|
|
| |
This function shouldn't be called when using a newer fuse
version, so we should not define it in that case.
|
|
|
|
|
|
|
| |
I believe this function call is resolved by the compiler, not
the linker, so this seems safer.
Thanks to Chris Clayton for spotting this.
|
|
|
|
|
| |
GCC 4.8 doesn't like to rename fuse_new_30 to fuse_new, if we
also define an implementation for fuse_new.
|
| |
|
|
|
|
|
| |
At least on Linux kernel 4.9, a value of zero gives more
than 1-sec accuracy.
|
|
|
|
| |
There is a proper meson-mode now.
|
|
|
|
| |
It's already set in meson.build as compiler flag.
|
|
|
|
|
|
| |
read() return value should always be positive or -1. However,
since we cast to unsigned a little later, it's clearer
to check for non-negativity.
|
|
|
|
|
|
|
|
| |
Some variables of different size and sign were getting compared
without any safe casting.
The build system also throws warnings at this and, being this
library used for filesystems, it's really important to ensure
stability.
|
|
|
| |
They were removed from source here: https://github.com/libfuse/libfuse/commit/73b6ff4b75cf1228ea61262c293fcb2fda5dfeea
|
|
|
|
|
|
| |
For example, FreeBSD doesn't have it.
Fixes: #173.
|
|
|
|
| |
Fixes: #160.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently libfuse has a hardcoded buffer limit to 128kib, while fuse
kernel module has a limit up to 32 pages.
This patch changes buffer limit to match the current page size, instead
of assuming 4096 bytes pages, enabling architectures with bigger pages
to use larger buffers, improving performance.
Also, add a new macro (HEADER_SIZE) to specify the space needed to
accommodate the header, making it easier to understand why those extra
4096 bytes are needed
Signed-off-by: Carlos Maiolino <cmaiolino-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
|
| |
|
| |
|
|
|
| |
Redundant copy when only op.read is available removed.
|
| |
|
|
|
|
|
|
|
| |
Apparently, NetBSD does not have /etc/mtab. Setting IGNORE_MTAB
in this case makes the code a little nicer.
See also https://github.com/libfuse/libfuse/pull/123
|
| |
|
| |
|
|
|
|
| |
documentation
|
| |
|
|
|
|
|
|
| |
-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.
|
|
|
|
| |
Fixes #116.
|
|
|
|
| |
Fixes #117.
|
|
|
|
|
|
| |
Enabled by default since we haven't released libfuse 3.0 yet :-).
Fixes #112.
|
|
|
|
| |
Fixes #112.
|
|
|
|
| |
See also issue #114.
|
|
|
|
|
| |
Instead of abort()ing, close the session properly and return an
error code.
|
| |
|