aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorLines
2024-02-26meson: Point OSX (darwin) to https://www.fuse-t.org/Bernd Schubert-1/+2
www.fuse-t.org is a more recent fuse extension for OSX based on NFS.
2024-02-26example/notify_store_retrieve: Fix races and handle errorsBernd Schubert-11/+38
This test was racy, the lookup counter must only be increased once kernel side has lookup completed and knows about the inode. However, this is still racy as app thread (python script) kernel-side libfuse thread kernel ---------------------------------------------------------------------- open file lookup req wait handle req reply wake app thread return new_inode() <continue file open> So actually on libfuse side even after returning from kernel side it is not ensured that the kernel has created the inode. I.e. using lookup_cnt in the test is still racy. A new variabled 'open_cnt' is added that is only increased in open Using open_cnt should be safe to use as kernel side (with atomic-open) first does lookup, from that data creates the inode and only then sends an open request. I.e. update_fs_loop() must only call fuse_lowlevel_notify_store() once it is absolutely sure kernel side has created the inode (open_cnt) and when it is sure the kernel inode still exists (lookup_cnt). Not really nice, but we actually need to accept some errors, as these still come up at umount time. Typically it is hard to hit, but tests in github actually frequently get it. Actually, it can be easily reproduced by commenting out the sleep line in update_fs_loop(). Underlying issue is that kernel side is sending ->destroy() only when it already internally released all inodes - too late for this test. The errors I run into are ENOENT and EBADFD, but I added back in ENODEV for safety. In order to avoid any other kind races mutex lock is also introduced.
2024-02-26Fix tests/test_write_cache in write back mode (#892)Bernd Schubert-8/+33
This test could fail whenever a something (kernel, userspace) decides to flush in between of two 2048B writes. These two writes are supposed to be merged into a single 4906 byte write by the kernel writeback cache, but _sometimes_ the test fails because 2048 byte writes get through. Fixes #882 Solution here is a modification how the test works - instead of requiring an exact aggregation of 2x2048B into 4096B, it now writes 64x2048B and requires in write-back modes the number of received writes requests is lower than 64 - we can expect that at least some writes get aggregated, but we do know how many. Co-authored-by: Bernd Schubert <bschubert@ddn.com>
2024-02-26Merge pull request #888 from yangyun50/masterBernd Schubert-4/+54
passthrough examples: enable direct io when open has flag: O_DIRECT
2024-02-26Enable direct IO for passthrough examples when open has flag O_DIRECTyangyun-0/+28
Shared locks (parallel_direct_writes) cannot be enabled for O_DIRECT, as O_DIRECT may be set past file open time with fcntl(fd, F_SETFD, ...). Kernel side fuse has precautions for shared lock direct-IO (direct_io in libfuse), as it needs an exclusive inode lock when direct and page cache IO happend at the same time. In order to enjoy the parallel_direct_writes feature (i.e., get a shared lock, not exclusive lock) for writes to the same file), direct_io is needed. The feature direct_io is corresponding to FOPEN_DIRECT_IO in fuse kernel. FOPEN_DIRECT_IO and O_DIRECT are not entirely the same as described above. So enable direct_io (i.e., FOPEN_DIRECT_IO in fuse kernel) to enjoy parallel direct_writes. Some patches related to FOPEN_DIRECT_IO and O_DIRECT are below: https://lore.kernel.org/all/753d6823-e984-4730-a126-d66b65ea772c@ddn.com
2024-02-24Passthrough options starting with "x-" to mtab (#894)Matthew-6/+54
This implements #651, tested with bindfs. "x-*" options are comments meant to be interpreted by userspace. #651 is about some 3rd party mount options like 'x-gvfs-notrash'. This also removes the test if /etc/mtab is a symlink. This test was added in commit 5f28cd15ab43c741f6d116be4d3a9aa5d82ab385 and the corresponding ChangeLog entry in this commit points to mount issues for read-only mtab. However, in all recent Linux distributions /etc/mtab is a symlink to /proc/self/mounts and never writable. In fact, util-linux 2.39 (libmount) entirely removed support for a writable mtab. At least since util-linux 2.19 (10-Feb-2011) /run/mount/utab is used as replacement for userspace mount entries..
2024-02-23passthrough_example: make parallel_direct_writes more clearlyyangyun-4/+26
Move the parallel_direct_writes enable action to the init function in high level API, it is more recommended just like commit 8ee553dac. Besides, add some comments to show that the feature parallel_direct_writes is depend on the feature direct_io (refer to kernel side patch series to consolidate direct IO, link: https://lwn.net/ml/linux-fsdevel/ 20230918150313.3845114-1-bschubert@ddn.com for the reason).
2024-02-20remove duplicated fuse_chan_put() (#893)yangyun50-2/+0
2024-01-29make FUSE_CAP_EXPIRE_ONLY test depend on available cap and not on versionHereThereBeDragons-2/+2
2024-01-29add support for kernel flag FUSE_HAS_EXPIRE_ONLYHereThereBeDragons-1/+1
2024-01-20Add processing for FUSE_CAP_HANDLE_KILLPRIV and disable it by defaultbigbrotherwei-2/+3
'FUSE_CAP_HANDLE_KILLPRIV' is not enabled by default anymore, as that would be a sudden security issue introduced by a new ABI and API compatible libfuse version.
2024-01-10Don't set FUSE_CAP_PARALLEL_DIROPS by defaultMiklos Szeredi-3/+0
Allowing parallel dir operations could result in a crash in a filesystem implementation that is not prepared for this. To be safe keep this flag off by default (this is not a regression, since there was no public release where this flag wasn't ignored). If the filesystem wants better performance, then it should set this flag explicitly. Fixes: c9905341ea34 ("Pass FUSE_PARALLEL_DIROPS to kernel (#861)") Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
2024-01-10Add FUSE_CAP_DIRECT_IO_ALLOW_MMAP and use in passthrough_hpBernd Schubert-0/+17
This is not called FUSE_CAP_DIRECT_IO_RELAX, as the kernel flag FUSE_DIRECT_IO_RELAX is supposed to be renamed to FUSE_DIRECT_IO_ALLOW_MMAP. The corresponding kernel patches just did not land yet.
2024-01-10Add in rename to FUSE_DIRECT_IO_ALLOW_MMAPBernd Schubert-4/+6
Add in the rename of FUSE_DIRECT_IO_RELAX to FUSE_DIRECT_IO_ALLOW_MMAP.
2024-01-10Synchronize fuse_kernel.h from current linux masterBernd Schubert-1/+62
2023-12-28examples/notify_store_retrieve: Add a clean shutdownBernd Schubert-11/+20
On shutdown update_fs_loop() was failing frequently in github test with ENOENT, but only ENODEV was tested for and only for the. With clean shutdown there is no need to test for such errors at all.
2023-12-17Allow *xattr operations on root directory (ino 1)amitgeron-5/+6
2023-11-19Clarify fuse_lowlevel poll() docstring (#862)George Hilliard-7/+10
The original docstring was confusing; it was not clear that the ph must be retained indefinitely, nor was it clear that the client *also* needs to reply to the poll call immediately. Clarify this by explaining that it is only necessary to retain a single handle, that the client must retain ph, and that it must immediately call reply.
2023-11-16Pass FUSE_PARALLEL_DIROPS to kernel (#861)fdinoff-0/+2
This tells the kernel that parallel lookup/readdir operations are supported. This is enabled by default but was not passed to the kernel so you always get the synchronized version.
2023-10-28Update fuse_common.h (#855)Caian Benedicto-1/+1
2023-10-25fuse_clone_chan: avoid additional FD_CLOEXEC setting if O_CLOEXEC defined (#852)legezywzh-0/+2
Since open(2) has been called with O_CLOEXEC flag if defined. Signed-off-by: Xiaoguang Wang <lege.wang@jaguarmicro.com> Co-authored-by: Xiaoguang Wang <lege.wang@jaguarmicro.com>
2023-10-25Bump actions/checkout from 4.1.0 to 4.1.1 (#854)dependabot[bot]-2/+2
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/8ade135a41bc03ea155e62e844d188df1ea18608...b4ffde65f46336ab88eb53be808477a3936bae11) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-10-12passthrough_hp: Fix clone-fd option (#850)SteveYang-0/+2
The clone-fd option is set valued but not used in the context. Use it in the code.
2023-10-11Enabled parallel direct IO writes for passthrough examplesBernd Schubert-0/+13
All these passthrough examples don't need writes to be serialized. Actually, most file systems probably handle non serialized parallel direct writes - the FOPEN_PARALLEL_DIRECT_WRITES flag is just to avoid a regression for those file system that rely on serialized DIO writes in fuse kernel. Passthrough file system forward the IO to another file system, which actually handles that internally - serialized in fuser kernel is not needed.
2023-10-10Fix typo in commentNikolaus Rath-1/+1
2023-10-10Released fuse-3.16.2Nikolaus Rath-4/+9
2023-10-09Fixes typo in fuse.h (#844)Nikola Petrov-1/+1
2023-09-26xfstests example: Use export in local.config and remove comment (#811)Bernd Schubert-13/+40
ix passthrough mount helper for running xfstests * The mount helper does not see the env vars exported by xfstests * Use the NFS style format TEST_DEV=source:/$TEST_SOURCE to communicate the sourse path to the mount helper without confusing xfstest * Also recognise when source= is provided in mount options * Support -o remount (e.g. for test generic/306) Signed-off-by: Amir Goldstein <amir73il@gmail.com> Co-authored-by: Bernd Schubert <bschubert@ddn.com> Co-authored-by: Amir Goldstein <amir73il@gmail.com> Co-authored-by: Nikolaus Rath <Nikolaus@rath.org>
2023-09-26Bump actions/checkout from 4.0.0 to 4.1.0dependabot[bot]-2/+2
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.0.0 to 4.1.0. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/3df4ab11eba7bda6032a0b82a6bb43b11571feac...8ade135a41bc03ea155e62e844d188df1ea18608) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-23passthrough-hp: Fix --clone-fdBernd Schubert-3/+2
Actually one had to use --clone-fd=1 instead of just --clone-fd.
2023-09-23passthough_hp: Add a direct-io optionBernd Schubert-2/+12
this is needed to test FOPEN_DIRECT_IO with xfstests. Also useful for some benchmarks.
2023-09-05Bump actions/checkout from 3.6.0 to 4.0.0 (#837)dependabot[bot]-2/+2
Bumps [actions/checkout](https://github.com/actions/checkout) from 3.6.0 to 4.0.0. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/f43a0e5ff2bd294095638e18286ca9a3d1956744...3df4ab11eba7bda6032a0b82a6bb43b11571feac) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-09-02Bump actions/checkout from 3.5.3 to 3.6.0 (#833)dependabot[bot]-2/+2
Bumps [actions/checkout](https://github.com/actions/checkout) from 3.5.3 to 3.6.0. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/c85c95e3d7251135ab7dc9ce3241c5835cc595a9...f43a0e5ff2bd294095638e18286ca9a3d1956744) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-08-25Add NTFS3 kernel driver fs to the whitelist of mount targets (#830)mrdvdrm-0/+1
With Linux Kernel 5.15 new ntfs kernel driver NTFS3 was included. It must be whitelisted as a permitted mount target.
2023-08-08Added missing file, update release process docs.Nikolaus Rath-4/+12
2023-08-08Released fuse-3.16.1Nikolaus Rath-3/+8
2023-08-08Don't attempt to put signify signature into gz headerNikolaus Rath-7/+6
This is currently buggy, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042837
2023-08-05Make errnum-verification more flexible (#824)ikbenlike-0/+5
Instead of hardcoding the value to check against, use a more dynamic method to verify the error number before passing it to the kernel.
2023-08-03Pass cache_readdir and keep_cache from high level API (#822)Aleksandr Mikhailov-0/+7
* Pass cache_readdir and keep_cache from high level API * Update ChangeLog.rst
2023-07-26Add dependabot for GHAPedro Kaj Kjellerup Nacht-0/+11
Signed-off-by: Pedro Kaj Kjellerup Nacht <pnacht@google.com>
2023-07-26Hash-pin workflow ActionsPedro Kaj Kjellerup Nacht-3/+3
Signed-off-by: Pedro Kaj Kjellerup Nacht <pnacht@google.com>
2023-07-07Allow linking with mold / fix the version script (#814)Bernd Schubert-2/+0
This fixes issue https://github.com/libfuse/libfuse/issues/810 and should avoid mold linking errors. Commit d4e294b removed made fuse_register_module() a static function, but forgot to remove it from the version script. Commit fe4f942 introduced copy_file_range to libfuse and added the non-exiting (neither declared nor defined) function fuse_reply_copy_file_range() to the version script. Kernel side just exects an integer reply how much was copied, using fuse_reply_write() as in fuse_lib_copy_file_range() is sufficient and no extra function is needed. Co-authored-by: Bernd Schubert <bschubert@ddn.com>
2023-07-05Use signify to sign releases.Nikolaus Rath-6/+78
2023-07-05Merge tag 'fuse-3.15.1'Nikolaus Rath-1/+17
2023-07-05Released fuse-3.15.1Nikolaus Rath-1/+17
2023-07-01Reduce default write size by halfNikolaus Rath-1/+1
Hopefully this will reduce test flakiness on CI.
2023-07-01Add missing include.Nikolaus Rath-0/+2
2023-06-30Make expire only function fail if no kernel support (#789)HereThereBeDragons-28/+86
2023-06-29Clarify behavior of fuse_session_exit().Nikolaus Rath-3/+6
2023-06-19Improve wording of user_allow_other usage instructions (#806)Waldir Pimenta-8/+8
* Improve wording of user_allow_other usage instructions * Remove dated comment from mount_max usage instructions
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-13 18:00:01 +0000