eBPF-based FUSE
summary
Implements a stacking file system that attaches a potential backing inode and a BPF program to each FUSE node so requests go through BPF pre/post filters before hitting user-space or the backing FS. Demonstrates pass-through for reads/writes that restores native read performance for selected files, and a location-redaction pipeline that zeroes EXIF GPS in reads by routing those ranges to user-space (with measurable performance cost). Patches are being prepared for submission and the plan is deployment in the next Android release.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 2:34Pass-through and x-views background
- 4:20Design of eBPF-based FUSE
- 7:29Use case: Hiding directories
- 8:52Use case: Location redaction
- 10:38Negative dentries and verifier challenges
- 12:02BPF helper functions and memory access
- 13:50Future directions and Q&A
related talks
19mExtension Framework for File Systems in User space
16mA file system for safely interacting with untrusted USB flash drives
21mModernizing Android BPF and the Android Security Model
24mFuse mounts recovery and Checkpoint/Restore
26mImprove FUSE Filesystem Performance and Reliability
16mBPF Based Telemetry, Metrics, and Accounting on Android
33meBPF: exploring use case of BPF kernel infrastructure
47mInto the Heart of the eBPF Hive!