Dan Nicholson c4738f8005 revokefs: Always bypass page cache for backend requests ...

By default, FUSE runs in cached I/O mode[1]. That means some I/O
responses will be taken from the page cache instead of being handled by
the FUSE process. For files opened for reading that's not a problem as
all the requests are just passed through.

However, that is problematic for files opened for writing since those
requests need to be handled by the backend. It's particularly bad for a
file opened `O_RDWR` since `read` responses from the page cache are
likely to be wrong. Instruct FUSE to use `direct-io` for those files so
that the page cache is bypassed.

1. https://docs.kernel.org/filesystems/fuse-io.html

Fixes: #5452

2023-06-28 13:26:27 +01:00

..

demo.c

Fix some warn_unused_result warnings

2021-10-12 13:50:14 -07:00

main.c

revokefs: Always bypass page cache for backend requests

2023-06-28 13:26:27 +01:00

Makefile.am.inc

automake: Consistently include $(AM_CFLAGS) in target-specific CFLAGS

2022-10-27 09:59:43 +01:00

meson.build

Add a Meson build system

2022-10-24 16:12:14 +01:00

writer.c

revokefs: Use correct format string for a ssize_t

2022-10-25 10:32:50 +02:00

writer.h

revokefs: Use FUSE version 3 if possible

2022-08-16 13:27:04 +02:00