aboutsummaryrefslogtreecommitdiffstats
path: root/ChangeLog.rst
AgeCommit message (Collapse)AuthorLines
2018-09-20Don't enable adaptive readdirplus unless fs has readdir() handler.Nikolaus Rath-0/+10
2018-08-31Released 3.2.6Nikolaus Rath-2/+2
2018-08-31Do not hardcode /etc/fuse.conf path.Nikolaus Rath-0/+3
2018-08-30Updated ChangeLog with recent changes.Nikolaus Rath-1/+8
2018-07-31Add autofs to mountpoint file system whitelistRobo Shimmer-0/+2
2018-07-24Released 3.2.5Nikolaus Rath-2/+7
2018-07-24Added ChangeLog entry for hardening patches.Nikolaus Rath-2/+6
2018-07-21Fix readdir() bug when a non-zero offset is specified in filler (#269)Rostislav-0/+8
The bug occurs when a filesystem client reads a directory until the end, seeks using seekdir() to some valid non-zero position and calls readdir(). A valid 'struct dirent *' is expected, but NULL is returned instead. Pseudocode demonstrating the bug: DIR *dp = opendir("some_dir"); struct dirent *de = readdir(dp); /* Get offset of the second entry */ long offset = telldir(dp); /* Read directory until the end */ while (de) de = readdir(de); seekdir(dp, offset); de = readdir(dp); /* de must contain the second entry, but NULL is returned instead */ The reason of the bug is that when the end of directory is reached, the kernel calls FUSE_READDIR op with an offset at the end of directory, so the filesystem's .readdir callback never calls the filler function, and we end up with dh->filled set to 1. After seekdir(), FUSE_READDIR is called again with a new offset, but this time the filesystem's .readdir callback is never called, and an empty reply is returned. Fix by setting dh->filled to 1 only when zero offsets are given to filler function.
2018-07-11Released 3.2.4Nikolaus Rath-2/+2
2018-05-18changelog: add info on rename deadlock fixBill Zissimopoulos-0/+5
2018-05-11Released 3.2.3Nikolaus Rath-0/+5
2018-03-31Fixed up duplicate ChangeLog entry.Nikolaus Rath-2/+0
2018-03-31Released 3.2.2Nikolaus Rath-0/+8
2017-12-01Handle mount ... -o nofail (#221)Josh Soref-0/+2
Accept (and ignore) nofail mount option
2017-11-27Spelling (#223)Josh Soref-1/+1
Fix spelling errors
2017-11-14Released 3.2.1Nikolaus Rath-0/+5
2017-09-12Released 3.2.0Nikolaus Rath-11/+11
2017-08-24Dropped support for building with autotoolsNikolaus Rath-0/+2
It's just too much pain to keep it working.
2017-08-24Add idle_threads mount option.Joseph Dodge-0/+7
2017-08-24Allow inode cache invalidation in high-level APISławek Rudnicki-0/+3
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.
2017-08-23Added examples/printcapNikolaus Rath-0/+3
2017-08-23fuse_loop_mt(): on error, return errno rather than -1.Nikolaus Rath-1/+4
2017-08-23fuse_loop(): don't return non-zero if there was no errorNikolaus Rath-0/+3
2017-08-22Document and unify error codes of fuse_lowlevel_notify_*Nikolaus Rath-0/+6
2017-08-22Make passthrough_fh work under FreeBSD.Nikolaus Rath-0/+2
2017-08-22Document meaning of zero telldir() offset.Nikolaus Rath-0/+3
2017-08-22Allow building without iconv.Nikolaus Rath-0/+2
cfg.has('HAVE_ICONV') was always true.
2017-08-14directly call fuse_new_31() instead of fuse_new() internallyuserwithuid-0/+2
this fixes building with lto, which failed since commit 503e32d01e4db00e90d7acfd81ab05386559069f
2017-08-14Fixed udev rules directory.Nikolaus Rath-1/+3
2017-08-11Don't pass --update to cpNikolaus Rath-0/+2
Doesn't work on FreeBSD, and not strictly necessary.
2017-08-07Fix support for FUSE_POSIX_ACLMarcin Sulikowski-0/+7
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>
2017-08-06Released 3.1.1Nikolaus Rath-3/+3
2017-08-06Added writeback cache to passthrough_llNikolaus Rath-0/+2
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.
2017-08-06Clarify how the filesystem should handle open/create flagsNikolaus Rath-0/+3
2017-08-03Added ChangeLog entry for FreeBSD commits.Nikolaus Rath-0/+3
2017-08-03Don't check st_nlink value for mkdirNikolaus Rath-0/+2
Some filesystems don't track this for directories. Fixes: #180.
2017-08-03Added changelog entry for symbol versioning fixes.Nikolaus Rath-0/+3
2017-08-03Added changelog entry for commit f0ecf.Nikolaus Rath-0/+3
2017-08-03Fix compilation on 32bit systemsNikolaus Rath-0/+6
Fixes: #185.
2017-07-08Released 3.1.0Nikolaus Rath-2/+2
2017-07-08Added public fuse_lib_help(), bumped minor versionNikolaus Rath-1/+5
2017-07-08Fixed description of struct fuse_conn_info->time_granNikolaus Rath-0/+3
At least on Linux kernel 4.9, a value of zero gives more than 1-sec accuracy.
2017-07-07Fixed typo in ChangelogNikolaus Rath-1/+1
2017-07-06Fixed bug in code example in ChangeLog.Nikolaus Rath-2/+2
2017-06-21Install init script in $DESTDIR/etc, not $prefix/$sysconfdirNikolaus Rath-0/+2
Fixes: #178.
2017-06-05examples/passthrough_ll: added support for create()Nikolaus Rath-2/+2
2017-06-05example/passthrough_ll: added write supportNikolaus Rath-0/+2
2017-05-25Document RENAME_EXCHANGE and RENAME_NOREPLACE flags.Nikolaus Rath-0/+4
2017-05-24fuse_signals.c: use new do_nothing function instead of SIG_IGNNikolaus Rath-0/+6
Fixes: #160.
2017-05-24Released libfuse 3.0.2Nikolaus Rath-0/+11