| Commit message (Collapse) | Author | Age |
|
|
|
| |
Taken from Linux kernel commit 27bcd37.
|
|
|
|
|
| |
This creates a separate device file descriptor for each processing thread,
which might improve performance.
|
| |
|
|
|
|
| |
See renameat2() system call in linux-3.15 and later kernels.
|
| |
|
|
|
|
|
|
| |
This allows the filesystem to specify the time granularity it
supports when the kernel is responsible for updating times
("writeback_cache" option).
|
|
|
|
|
| |
Asynchronous direct I/O is supported by linux kernels 3.13 and
later, writeback caching is supported by 3.14 and later.
|
|
|
|
|
| |
Check for __KERNEL__ instead of __linux__ and use the standard int
types instead of the linux specific ones.
|
|
|
|
|
|
|
|
|
|
|
| |
This switches the -o no_readdirplus option to a tristate
string: -o readdirplus=(yes|no|auto)
Telling the kernel to always use readdirplus is beneficial to
filesystems (e.g. GlusterFS) where the cost to perform readdir
and readdirplus are identical.
The default remains "auto" (if supported).
|
|
|
|
|
| |
Make requested poll events available to the filesystem. If the requested
eventsare not available, then this field is zero.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch implements readdirplus support in FUSE usersapce. It adds
a new fuse lowlevel operations fuse_lowleve_ops::readdir_plus,
corespoding mount options and helper functions to maintain buffer.
[From: Eric Wong <normalperson@yhbt.net>]
This makes our terminology consistent with NFS and
our kernel module, as well as reducing user/developer
confusion in the command-line.
Note: I'm keeping "fuse_add_direntry_plus" since that is
less standardized in its use than "readdirplus" for now.
Signed-off-by: Feng Shuo <steve.shuo.feng@gmail.com>
|
|
|
|
|
| |
Use <linux/types.h> for linux and define types used for other operating systems
using <stdint.h> types.
|
|
|
|
|
|
|
|
|
|
|
| |
Several caching logic changes have been made on the kernel side
to better support network-based fuse filesystems. These include
kernel side mtime checking and read path cache revalidation. The
new caching logic is enabled through the FUSE_AUTO_INVAL_DATA
init flag. Export this to the user via the '[no_]auto_inval_data'
mount option.
Signed-off-by: Feng Shuo <steve.shuo.feng@gmail.com>
|
|
|
|
|
| |
Add missing flags that userspace derived from the protocol version number. This
makes the protocol more flexible.
|
|
|
|
|
|
| |
fallocate filesystem operation preallocates media space for the given file.
If fallocate returns success then any subsequent write to the given range
never fails with 'not enough space' error.
|
|
|
|
|
| |
Use the ISO C standard compliant form instead of the gcc extension in the
interface definition.
|
|
|
|
|
|
|
|
|
|
| |
This partially reverts commit 4b2157c44e6ad7e692fcffb7450143e83151d36b.
Remove mmap/munmap suppor as this missed the interface changes for Linux-3.3
(API version 7.18).
Only revert the mmap/munmap bits and leave the retrieve_reply API fix in place
as well as the optimization in fuse_send_data_iov_fallback().
|
|
|
|
|
|
|
|
|
| |
libfuse part to allow a FUSE file-system to tell the kernel when a
file or directory is deleted. If the specified dentry has the
specified inode number, the kernel will unhash it.
Signed-off-by: John Muir <john@jmuir.com>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
|
|
|
|
|
| |
Currently this is only useful for CUSE. Also update retrieve_reply()
method.
|
|
|
|
| |
Reported by Antonio SJ Musumeci
|
|
|
|
|
|
|
|
|
|
| |
This fixes problems with emulating flock() with POSIX locking.
Reported by Sebastian Pipping.
As with lock/setlk/getlk most filesystems don't need to implement
this, as the kernel takes care of file locking. The only reason to
implement locking operations is for network filesystems which want
file locking to work between clients.
|
|
|
|
|
| |
Fix the ambiguity of ioctl ABI on the kernel/userspace boundary
for 32bit vs. 64bit userspace
|
|
|
|
|
| |
This allows forget requests to be processed faster and doesn't require
a modification to fuse filesystems. Reported by Terje Malmedal
|
|
|
|
| |
Retrieve data stored in the kernel buffers for a given inode.
|
|
|
|
| |
Request data to be stored in the kernel buffers for a given inode.
|
| |
|
|
|
|
| |
threshold tunable.
|
|
|
|
|
| |
kernel and userspace. Notably libfuse didn't correctly handle the
case when the supported major versions didn't match
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for mknod, mkdir and create requests by linux kernel version
2.6.31 or later, otherwise the umask is set to zero. Also
introduce a new feature flag: FUSE_CAP_DONT_MASK. If the kernel
supports this feature, then this flag will be set in conn->capable
in the ->init() method. If the filesystem sets this flag in in
conn->want, then the create modes will not be masked.
* Add low level interfaces for lookup cache and attribute
invalidation. This feature is available in linux kernels 2.6.31
or later. Patch by John Muir
* Kernel interface version is now 7.12
|
| |
|
| |
|
|
|
|
|
|
|
| |
"restricted" ioctls are supported (which are defined with the
_IO(), _IOR(), _IOW() or _IOWR() macros). Unrestricted ioctls
will only be allwed to CUSE (Character Device in Userspace)
servers. Patch by Tejun Heo
|
|
|
|
| |
not seekable. Patch by Tejun Heo
|
|
|