1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
//! An NFSv3 server: [nfsserve] 0.11.0 (BSD-3-Clause, see `LICENSE` here), copied in
//! so it can be changed here first. Changes from upstream:
//!
//! - [`transaction_tracker`] drops old transactions once a second instead of on every
//! call, whose cost grew with the number of calls a minute and took most of the
//! server's time under load: a cold Rust build on the mount took 65 s with it and
//! 14 s without.
//! - A listing's entry may come without attributes ([`vfs::DirEntry::attr`]), which
//! READDIRPLUS allows, so a listing needn't work out every file's size.
//! - The generation number is a `OnceLock` instead of a `static mut`, as sandfs
//! forbids unsafe code.
//! - Each call can be checked, answered or have its reply changed before it reaches
//! the server ([`context::CallFilter`]), which sandfs used to do in a relay in front
//! of it, costing every call a second trip over the loopback.
//! - Messages over 2 MiB are refused instead of read whole, closing the connection
//! (which upstream left open, reading on), and a reply goes out in one write instead
//! of two (its record mark, then the rest).
//! - A listing's entries carry cookies of their own ([`vfs::DirEntry::cookie`])
//! instead of their file ids, which two names of one file share, and READDIR
//! resumes from the cookie it is given instead of starting over.
//! - LINK (hard links) is answered, through [`vfs::NFSFileSystem::link`], which
//! upstream left unimplemented, and PATHCONF says how many names a file may have.
//! - Left out: `fs_util` and the `filetime` conversion, which sandfs doesn't use.
//!
//! [nfsserve]: https://github.com/huggingface/nfsserve