Safe Systems with Linux
summary
Proposal embeds machine‑readable requirements into kernel source using an SPDX:W requirement header with unique IDs so tests, files and configs can link into a traceability database. Tooling includes basil for requirements management, a kernel static analysis Navigator, and a CI pipeline (Docker + GitLab CI + Yocto/Octo) that builds reproducible images and generates SBOMs. A dynamic workload tracing prototype is dynamic workload tracing upstreamed to kernel docs; AGL images run on Raspberry Pi 5, full hardware reference currently costs ~$3–5k.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:53Functional safety standards
- 10:59Reproducible safety systems
- 18:22Requirements traceability
- 27:12Kernel requirement identifiers
- 36:29Open source safety docs
related talks
45mLooking at Linux as a SEooC
34mKernelSBOM: Reconstructing Linux Kernel Builds into Trusted SPDX Bills of Materi...
02mSafe Systems with Linux MC Wrap up and next steps
33mAutomation of SBOM Assessment in AGL Development Process
41mCross Industry Demands and Collaboration Opportunities
32mImplementing and Validating Linux Cyber Security Requirements: SEAPATH, a Case Study
26mApplication of the Upcoming SPDX Safety Profile
46mA Maintainable, Scalable, and Verifiable SW Qualification Approach for Automotive in Linux