Dan Nicholson b6e376f6d1 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
(cherry picked from commit c4738f8005)
2023-11-14 21:29:06 +00:00
2019-04-08 12:50:42 +00:00
2023-02-18 14:08:27 +00:00
2021-03-10 10:33:51 +01:00
2018-02-05 15:21:40 +00:00
2023-03-16 09:55:13 +00:00
2015-03-31 15:36:29 +01:00
2022-10-28 13:07:15 +01:00
2023-03-16 09:55:13 +00:00

Flatpak icon

Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux.

See https://flatpak.org/ for more information.

Community discussion happens in #flatpak:matrix.org, on the mailing list, and on the Flathub Discourse.

Read documentation for Flatpak here.

Contributing

Flatpak welcomes contributions from anyone! Here are some ways you can help:

Hacking

See CONTRIBUTING.md

Related Projects

Here are some notable projects in the Flatpak ecosystem:

  • Flatseal: An app for managing permissions of Flatpak apps without using the CLI
  • Flat-manager: A tool for managing Flatpak repositories
Description
No description provided
Readme 68 MiB
Languages
C 91%
Shell 5.1%
Python 1.8%
Meson 1.2%
Yacc 0.8%