So you're a Linux kernel developer? Name all subsystems.
summary
Researchers mine MAINTAINERS and git history to build a section graph where vertices are maintainer sections and edges mean shared lines of code; they run walktrap clustering on the top 20 sections to detect de-facto subsystems, measure conforming integration (whether relevant maintainers merged a patch), and find concrete mis- and non-conforming examples inside DRM and media clusters. Results feed safety-certification evidence for ELISA and are reproducible via tools on GitHub at lfd/pasta.
AI-written summary Β· about
chapters (17)
- 0:00Introduction
- 1:20Motivation and Goals
- 2:20Safety Critical Certification
- 4:02Open Development Process
- 5:24Maintenance Hierarchy
- 7:20Crosscutting Patches
- 7:45The Problem
- 8:43What is a subsystem
- 9:25Media Subsystem
- 10:52Subsystem Definition
- 11:45Subsystem Detection
- 14:02Section Graph
- 15:08Section Graph Example
- 15:40Cluster Discussion
- 23:25Patch Integration
- 27:36Future work
- 36:35Disclaimer
related talks
41mSo you're a Linux kernel developer? Name all subsystems.
44mPanel Discussion: Enabling Linux in Safety Applications
31mEnhancing Kernel Functional Safety Analysis with KS-nav
36mLinux Kernel Developer Panel
48mLinux Kernel Developer Panel
25mLinux: Where Are We Going
25mA Conversation with Linus Torvalds
42mBoF: Safety + Open Source Software: Where it Started & Where It's Going
