Adding Testable Code Specifications in the Linux Ke...
summary
Proposal creates a machine‑readable kernel-doc format for testable expectations that ties declared intent to tests and coverage via a checksum/hash linking so CI alerts on drift. Uses existing tools (syzkaller, kselftest, KUnit, llvm-cov/gcov), shows a small ftrace review (10% of one file) that produced one mainline fix and several docs patches, and argues a virtuous cycle of intent → test → coverage → maintainer signoff to make intent traceable rather than emergent.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Linux kernel metrics
- 4:12Case study Ftrace analysis
- 8:06Semantic gap problem
- 12:42Current documentation methods
- 15:11Testable expectations concept
- 20:10Template and checksum method
- 24:44Process and maintenance
- 27:33Call to action
- 27:54Q&A session
related talks
53mDocumenting the Design of the Linux Kernel
19mChecking your work: Linux kernel testing and CI
15mLinux Testing made better with DATA
30mKernel Testing with KUnit: Bridging the Gap
50mTips for Writing Good Tests for Linux- 15m"Linux Testing made better with DATA"
34mLinux Kernel Testing: Providing Better Results to the Upstream Community- 34mLinux Kernel Testing: Providing Better Results to the Upstream Community