| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
update_fs_loop() is still running when the filesystem unmounts,
but it that case calls to fuse_lowlevel_notify_* will fail.
Fixes: #105.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 179fa13b40387645e722089873079488f9dbe3d8.
|
|
|
|
|
|
|
|
|
|
| |
Since RELEASE requests are asynchronous, it is possible that libfuse
still considers the file to be open when userspace has closed it, so
that a successive unlink() call from userspace actually triggers
a rename(). We avoid the resulting test failure by re-trying a few
times.
Fixes: #157.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
We can consider changing the code to drop the requirement if it
turns out that there's a system where this isn't given.
Fixes issue #167.
|
| |
|
|
|
|
| |
Hopefully this helps debugging issue #157.
|
|
|
| |
They were removed from source here: https://github.com/libfuse/libfuse/commit/73b6ff4b75cf1228ea61262c293fcb2fda5dfeea
|
|
|
|
| |
This should help debugging issue #157.
|
|
|
|
|
| |
Slightly increases coverage of examples/passthrough_ll.c (which
supports open for reading, but not for writing).
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In particular, don't call it "user_data" in one place and
"private_data" elsewhere.
Changing the name of the variable in the prototype should not affect
backwards compatibility.
Fixes: #155.
|
| |
|
| |
|
| |
|
|
|
|
| |
Together with the previous commit, this fixes #156.
|