Enhancing Kernel Functional Safety Analysis with KS-nav
summary
ks-nav reverse-engineers a Linux kernel binary to produce call and subsystem graphs that pinpoint which files and drivers (via the MAINTAINERS map) participate in an API, highlights global-data-sharing diagrams, and links nodes back to source lines via debug info. It uses binary cross‑reference tooling to avoid config/compiler surprises, produces static views useful for expert FMEA, proves workable in live demos, and plans version-diffing via automated builds though mantainer file coverage can be incomplete.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:25Purpose of KS-nav
- 2:50Need for KS-nav in kernel analysis
- 7:10Linux kernel subsystems
- 10:29KS-nav architecture
- 12:36Binary vs source analysis
- 14:47KS-nav for safety analysis
- 18:09Live demo of KS-nav
- 22:35Future KS-nav features
- 26:38Q&A
related talks
45mLooking at Linux as a SEooC
31mBypassing Anti-Debugging: A Hybrid Real-Simulated Approach to Rootkit Analysis
32mPruning Kernel CVEs With Code Reachability Analysis
41mSo you're a Linux kernel developer? Name all subsystems.
38mSafe Systems with Linux
59mSanitizing the Linux Kernel — On KASAN and other Dynamic Bug-finding Tools
08mWIP: QKSAN: Towards Multiple Sanitizers for In-vehicle COTS OS Kernels
05mLightning Talk: Pruning the Kernel CVEs With Code Reachability Analysis