aboutsummaryrefslogtreecommitdiffstats
path: root/lib/fuse_versionscript
diff options
context:
space:
mode:
authorAlan Somers <asomers@gmail.com>2019-11-03 02:44:12 -0700
committerNikolaus Rath <Nikolaus@rath.org>2019-11-03 09:44:12 +0000
commitb9c584370aa489ac00b1e8a0454c61f30c0531af (patch)
tree0591be59b16b6e2e33cd92bf0b235d1ccfe45747 /lib/fuse_versionscript
parentfa0981fe80b037cdd923f3d87157e78f9e1222a9 (diff)
downloadlibfuse-b9c584370aa489ac00b1e8a0454c61f30c0531af.tar.gz
Use the -o intr mount option on FreeBSD (#462)
FUSE file systems normally indicate their interruptibility by returning ENOSYS to the first FUSE_INTERRUPT operation. But that causes two problems for file systems that aren't interruptible: 1) A process may block on a signal, even if another thread could've handled the signal. The kernel must know whether the FUSE thread is interruptible before deciding which thread should receive a signal. 2) The protocol allows a FUSE daemon to simply ignore FUSE_INTERRUPT operations. From the kernel's point of view, that is indistinguishable from a FUSE_INTERRUPT operation arriving after the original operation had already completed. Thus, the kernel can't interpret an ignored FUSE_INTERRUPT as an indication that the daemon is non-interruptible. With the -o nointr mount option, no FUSE_INTERRUPT operations will ever be sent. Most FUSE file systems should require no modifications to take advantage of this mount option.
Diffstat (limited to 'lib/fuse_versionscript')
0 files changed, 0 insertions, 0 deletions