diff options
| author | gVisor bot <gvisor-bot@google.com> | 2020-05-28 09:21:31 -0700 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-05-28 09:21:31 -0700 |
| commit | 2fe14b484a662cdc8eec8d6dd5bd5fe6492ba630 (patch) | |
| tree | cb800d4a4fdc6422374878b1568a64da873f42a3 /pkg/sentry/fs/g3doc | |
| parent | 32021bce9607e09f3d21d3d28047d49340da231e (diff) | |
| parent | 17d500f907c7bfc4d8365cceb4b305e9e3e6733c (diff) | |
Merge pull request #2792 from avagin:g3doc/fuse/refs
PiperOrigin-RevId: 313600051
Diffstat (limited to 'pkg/sentry/fs/g3doc')
| -rw-r--r-- | pkg/sentry/fs/g3doc/fuse.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/pkg/sentry/fs/g3doc/fuse.md b/pkg/sentry/fs/g3doc/fuse.md index 635cc009b..b43c082a7 100644 --- a/pkg/sentry/fs/g3doc/fuse.md +++ b/pkg/sentry/fs/g3doc/fuse.md @@ -99,7 +99,7 @@ ops can be implemented in parallel. ## FUSE Protocol The FUSE protocol is a request-response protocol. All requests are initiated by -the client. The wire-format for the protocol is raw c structs serialized to +the client. The wire-format for the protocol is raw C structs serialized to memory. All FUSE requests begin with the following request header: @@ -255,6 +255,8 @@ I/O syscalls like `read(2)`, `write(2)` and `mmap(2)`. # References -- `fuse(4)` manpage. -- Linux kernel FUSE documentation: - https://www.kernel.org/doc/html/latest/filesystems/fuse.html +- [fuse(4) Linux manual page](https://www.man7.org/linux/man-pages/man4/fuse.4.html) +- [Linux kernel FUSE documentation](https://www.kernel.org/doc/html/latest/filesystems/fuse.html) +- [The reference implementation of the Linux FUSE (Filesystem in Userspace) + interface](https://github.com/libfuse/libfuse) +- [The kernel interface of FUSE](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/fuse.h) |