| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This fixes issue #191 (where the test was done by simply adding
FUSE_CAP_WRITEBACK_CACHE without adjusting the flags in the
open() call).
Fixes: #191.
|
| |
|
|
|
|
|
|
| |
As the comment says, this made it compile but not work. If there is a
need, we can add these checks to meson.build to only build this file
if the prerequisites are satisfied.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: #186.
|
|
|
|
|
|
| |
Some filesystems don't track this for directories.
Fixes: #180.
|
| |
|
| |
|
|
|
|
| |
Fixes: #185.
|
| |
|
|
|
|
| |
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.
|
|
|
|
| |
This is safer than making assumptions.
|
|
|
|
| |
There is a proper meson-mode now.
|
| |
|
|
|
|
| |
It's already set in meson.build as compiler flag.
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: #178.
|
|
|
|
| |
The previous code didn't actually go through the mountpoint at all.
|
|
|
|
|
| |
When changes always come through kernel, timeouts
should be large.
|
| |
|
|
|
|
|
|
| |
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.
|