leetbit
References

Collected knowledge

The sources the system stands on. Every reference links back to everything that cites it.

Books

Linux Kernel Development, 3rd editioncited by 0
Robert Love · 2010
Addison-Wesley. Chapters 12–13 cover the VFS and block I/O; dated in places, still the clearest prose introduction.

The book I keep returning to when kernel documentation assumes too much context. Its VFS chapters are the scaffolding under both filesystem articles.

Cited by

Papers

Soft Updates: A Technique for Eliminating Most Synchronous Writes in the Fast Filesystemcited by 0
G. R. Ganger, M. K. McKusick, C. A. N. Soules, Y. N. Patt · 1999
USENIX ATC. Dependency tracking in memory to preserve metadata consistency without sync writes — the intellectual ancestor of every journaling tradeoff.

Queued behind the ext4 journaling notes; the dependency-graph idea echoes in the knowledge-graph work.

Cited by

Specifications

POSIX.1-2017 (IEEE 1003.1-2017)cited by 0
IEEE / The Open Group · 2018
The base specification: system call and path-resolution semantics that Linux implements and occasionally deviates from.

Pathname resolution is specified in §4.13 and per-call. Reading the spec after reading namei.c explains which kernel behaviors are obligations and which are choices.

Cited by

RFCs

RFC 8259 — The JavaScript Object Notation (JSON) Data Interchange Formatcited by 0
T. Bray, ed. · 2017
IETF STD 90. The JSON grammar, obsoleting RFC 7159.

Cited by the search index format notes; mostly here as an example of how RFCs are catalogued.

Cited by

Kernel documentation

Documentation/filesystem/vfs.rstcited by 0
The Linux kernel community · 2024
In-tree VFS documentation, kernel v6.9. The authoritative description of the struct inode / dentry / file object model.

Terse, precise, occasionally wrong in small ways. Always read alongside the actual fs/namei.c source.

Source ↗

Cited by
Documentation/filesystem/fuse.rstcited by 1
The Linux kernel community · 2024
The FUSE kernel module documentation: protocol messages, request lifecycle, invalidation semantics.

Required reading before writing a single line of a FUSE daemon. The invalidation section is easy to miss and expensive to learn the hard way.

Cited by
projectmemory process schedular
fs/namei.c — path_lookupat() and friendscited by 0
The Linux kernel community · 2024
Linux v6.9.6. The in-tree pathname-resolution walk: link_path_walk, walk_component, and the RCU-walk fast path.

The source of record for how a path actually becomes an inode; read directly rather than through prose, because the object model only fully makes sense inside the walk loop itself.

Cited by
perf-stat(1)cited by 0
The Linux kernel community · 2024
Linux manual page. The event-counting interface (perf stat) for hardware and software events around a workload.

The tool behind the dentry hit-rate measurements; its event semantics differing across kernel versions is exactly the methodology hole the dentry-cache notes flag.

Cited by

Websites

fuser — a Rust library for filesystems in userspacecited by 1
Christopher Berner and contributors · 2024
Rust implementation of the FUSE protocol: the session loop and request dispatch atlas-fs is built on.

Chosen over libfuse/C in atlas-fs ADR-001. Reading its request handlers is the fastest way to see what the kernel actually asks a FUSE daemon to do.

Source ↗

Cited by
projectmemory process schedular