src-test/sbin/mount_fusefs, branch mainFreeBSD source treehttps://cgit-dev.freebsd.org/src-test/atom?h=main2019-12-07T15:17:00ZCorrect a handful of typos/grammos.2019-12-07T15:17:00ZJens Schweikhardtschweikh@FreeBSD.org2019-12-07T15:17:00Zurn:sha1:e7114e1e1196732973b2ae73b325982ad0024582mount_fusefs: fix a segfault on memory allocation failure2019-09-07T21:49:01ZAlan Somersasomers@FreeBSD.org2019-09-07T21:49:01Zurn:sha1:8c50ee012fbc71aa640ed437d7fe0891793b4fd7
Reported by: Coverity
Coverity CID: 1354188
MFC after: 4 days
Sponsored by: The FreeBSD Foundation
fusefs: proofread man pages2019-07-31T16:07:16ZAlan Somersasomers@FreeBSD.org2019-07-31T16:07:16Zurn:sha1:db90284c3187f638dacb430683c3531b76d09cfc
Reported by: bcr, mandoc, textproc/igor
Sponsored by: The FreeBSD Foundation
fusefs: add a intr/nointr mount option2019-07-18T17:55:13ZAlan Somersasomers@FreeBSD.org2019-07-18T17:55:13Zurn:sha1:ed74f781c9f704092556f860a00b0bb53fdedff7
FUSE file systems can optionally support interrupting outstanding
operations. However, the file system does not identify to the kernel at
mount time whether it's capable of doing that. Instead it signals its
noncapability by returning ENOSYS to the first FUSE_INTERRUPT operation it
receives. That's a problem for reliable signal delivery, because the kernel
must choose which thread should get a signal before it knows whether the
FUSE server can handle interrupts. The problem is even worse because the
FUSE protocol allows a file system to simply ignore all FUSE_INTERRUPT
operations.
Fix the signal delivery logic by making interruptibility an opt-in mount
option. This will require a corresponding change to libfuse, but not to
most file systems that link to libfuse.
Bump __FreeBSD_version due to the new mount option.
Sponsored by: The FreeBSD Foundation
[skip ci] update copyright headers in fusefs files2019-06-28T04:18:10ZAlan Somersasomers@FreeBSD.org2019-06-28T04:18:10Zurn:sha1:8aafc8c3894e5d5d302bd04d88aec04d719b4377
Sponsored by: The FreeBSD Foundation
fusefs: enable write clustering2019-06-14T18:14:51ZAlan Somersasomers@FreeBSD.org2019-06-14T18:14:51Zurn:sha1:8eecd9ce05ee9744ebf9ecd0c2d1d2431b9fe06c
Enable write clustering in fusefs whenever cache mode is set to writeback
and the "async" mount option is used. With default values for MAXPHYS,
DFLTPHYS, and the fuse max_write mount parameter, that means sequential
writes will now be written 128KB at a time instead of 64KB.
Also, add a regression test for PR 238565, a panic during unmount that
probably affects UFS, ext2, and msdosfs as well as fusefs.
PR: 238565
Sponsored by: The FreeBSD Foundation
mount_fusefs(8): document the -o subtype option.2019-05-20T15:58:44ZAlan Somersasomers@FreeBSD.org2019-05-20T15:58:44Zurn:sha1:2019f75c322a6490fa114ec5af2c92090b106a64
Sponsored by: The FreeBSD Foundation
mount_fusefs(8): fix inverted condition check from r3475442019-05-15T00:15:40ZAlan Somersasomers@FreeBSD.org2019-05-15T00:15:40Zurn:sha1:341346b039827d4897a95a421597f6c8c0f79691
Sponsored by: The FreeBSD Foundation
fusefs: reap dead sysctls2019-05-13T19:03:46ZAlan Somersasomers@FreeBSD.org2019-05-13T19:03:46Zurn:sha1:4abf87666ad69ba377a7d0aa71e87bc8824759fa
Remove the "sync_unmount" and "init_backgrounded" sysctls and the associated
options from mount_fusefs. Add no backwards-compatibility hidden options to
mount_fusefs because these options never had any effect, and are therefore
unlikely to be used.
Sponsored by: The FreeBSD Foundation
Rename fuse(4) to fusefs(4)2019-03-20T21:48:43ZAlan Somersasomers@FreeBSD.org2019-03-20T21:48:43Zurn:sha1:123af6ec70016f5556da5972d4d63c7d175c06d3
This makes it more consistent with other filesystems, which all end in "fs",
and more consistent with its mount helper, which is already named
"mount_fusefs".
Reviewed by: cem, rgrimes
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D19649