aboutsummaryrefslogtreecommitdiffstats
path: root/lib/modules
AgeCommit message (Collapse)AuthorLines
2016-10-20Turn fuse_operations.nopath_flag into fuse_config.nullpath_okNikolaus Rath-4/+4
Modifying struct fuse_config in the init() handler is the canonical way to adjust file-system implementation specific settings. There is no need to have flags in struct fuse_operations.
2016-10-20Pass struct fuse_config to high-level init() handler.Nikolaus Rath-4/+6
2016-10-15Pass fuse_file_info to getattr, chown, chmod, truncate, utimens handlersNikolaus Rath-75/+29
This obsoletes the ftruncate & fgetattr handlers. Fixes #58.
2014-07-15libfuse: add flags to ->rename()Miklos Szeredi-4/+4
See renameat2() system call in linux-3.15 and later kernels.
2014-03-05libfuse: implement readdirplus for high-level APIEric Wong-6/+9
Reuse the old "readdir" callback, but add a flags argument, that has FUSE_READDIR_PLUS in case this is a "plus" version. Filesystems can safely ignore this flag, but if they want they can add optimizations based on it: i.e. only retrieve the full attributes in PLUS mode. The filler function is also given a flags argument and the filesystem can set FUSE_FILL_DIR_PLUS if all the attributes in "stat" are valid.
2013-07-26Print help on stdout instead of stderrMiklos Szeredi-2/+2
2013-07-24libfuse: remove "-D_FILE_OFFSET_BITS=64" from fuse.pcMiklos Szeredi-0/+4
add AC_SYS_LARGEFILE to your configure.ac instead.
2012-07-20Remove compatibility path handlingMiklos Szeredi-2/+0
This means that now NULL is a valid path for operations that take a file descriptor if the file was unlinked and hard_remove option is specified.
2012-07-19Start of 3.0 seriesMiklos Szeredi-2/+2
Change the version numbers. This is going to be a new major version of the library breaking backward compatibility on the binary level as well as the source level.
2012-07-04libfuse: mark some data constantMiklos Szeredi-4/+4
2011-07-06Add ->flock() operation to low and high level interfacesMiklos Szeredi-0/+26
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.
2011-03-30Fix a possible resource leak (free the old up)Laszlo Papp-0/+4
2010-11-10add read_buf method to high level APIMiklos Szeredi-8/+8
Add a new read_buf() method to the highlevel API. This allows returning a generic buffer from the read method, which in turn allows zero copy reads.
2010-11-10add write_buf method to high level APIMiklos Szeredi-7/+7
Add new write_buf() method to the highlevel API. Similarly to the lowlevel write_buf() method, this allows implementing zero copy writes.
2010-06-15* Add a nopath option and flag, indicating that path argumentMiklos Szeredi-0/+2
need not be calculated for the following operations: read, write, flush, release, fsync, readdir, releasedir, fsyncdir, ftruncate, fgetattr, lock, ioctl and poll.
2008-02-08Support receiving file handle from kernel in GETATTR request; Allow ↵Miklos Szeredi-120/+150
operations with a NULL path argument, if the filesystem supports it
2007-12-12change indentingMiklos Szeredi-965/+969
2007-10-16Clarify licence version to be "LGPLv2" for the libraryMiklos Szeredi-2/+2
2007-05-11update flush changesMiklos Szeredi-1/+1
2007-04-28docMiklos Szeredi-3/+17
2007-02-03Add filesystem stacking support to high level APIMiklos Szeredi-0/+1356
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-07 20:27:55 +0000