Looking at Linux as a SEooC
summary
Linux is being treated as a safety element out of context with concrete steps: the kernel sees 9 changes per hour from ~4,700 unique contributors, so the project focuses on minimal kernels, formalized kernel requirements and automated evidence. Tools and outputs include SPDX 3.1 for functional safety metadata, LLVM code-coverage patches and object-level mapping, plus a KNAF-style analysis to enumerate reachable call trees. The goal targets DO-178C DAL A compliance; work is partial but producing testable requirements and reproducible artifacts.
AI-written summary · about
chapters (6)
- 0:00Linux as SEooC
- 6:22Linux in safety contexts
- 10:21System integrator SEooC duties
- 20:41Linux kernel safety assurance
- 34:43Call for Linux safety certification
- 43:55Linux in safety-critical future
related talks
32mDeveloping Open Source for Safety and Security
38mSafe Systems with Linux
35mOpen Sesame! Why Functional Safety is the Master Key to Open the Door for Linux into Automotive
02mSafe Systems with Linux MC Wrap up and next steps
36mAligning Automotive Standards with Open Source Excellence
01h 00mPanel Discussion: What is Lacking in Linux Security and What Are or Should We be Doing about This
01h 07mPanel Discussion: What is Lacking in Linux Security and What Are or Should We be Doing about This
32mImplementing and Validating Linux Cyber Security Requirements: SEAPATH, a Case Study