Clean-up on Aisle "fsconfig(2)"
summary
Man pages for the “new” mount API finally land, and the talk calls out concrete gaps: FSCONFIG_SET_PATH and FSCONFIG_SET_PATH_EMPTY are effectively unused but needed to avoid race attacks; FSCONFIG_CMD_CREATE_EXCL returns an error without actionable info for singleton superblocks; FC log uses an eight-entry ring buffer with no drop notification; FS context enters an unrecoverable fail state so runtimes must rebuild contexts. Proposes unified helpers for path/FD, per-filesystem callbacks to report ignored options, and structured/pollable log output or bigger buffers.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 6:34FS config parameter limitations
- 15:42Singleton mount issues
- 20:19FS context log limitations
- 27:02FS context failure state problems
- 34:25Q&A and wrap-up
related talks
29mFilesystem mounts in user namespaces
26mDive into Apple UserFS (Userspace Filesystem)
39mSecure Path Operations and Libpathrs
35mOverview and Recent Developments: Namespaces and Capabilities
29mCF Volume Services - Building for Failure, Security and Performance
38mHow I started chasing speculative type confusion bugs in the kernel and ended up wi...
48mUpdate on Landlock: IOCTL Support
41mThe State and Direction of LSM Stacking