Finding the Best Way to Use Linux Kernel - Status Update
summary
State of Linux kernel: release cadence averages ~63 days so five-point-two -> 5.2.9 pattern repeats, upstream is the only accepted source and patches must go there; long-term support (LTS) kernels get extended maintenance now often to six years with Greg Kroah‑Hartman handling many releases; example footprints: 12,000 commits in 4.4 and ~30,000 in 4.9; major users (Android, Raspberry Pi, Amazon, WSL2) standardize on LTS; recommended workflow is push fixes upstream, adopt an LTS, run automated suites (LTP, shared test harnesses, kernelci), and track CPU-class vulnerabilities like Spectre/MDS.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:25Who am I
- 1:53Development Community
- 3:31Latest Status
- 4:46Release Candidate
- 5:26Release Timeline
- 7:43Linux Kernel Development Policy
- 9:11Linux Kernel Development Process
- 10:49Linux Kernel Code Growth
- 13:58Current Situation
- 15:12Release Date
- 16:08Release History
- 20:27Number of Comets
- 22:28Number of Patches
- 23:01Automated Testing
- 25:17Recommended Step
- 26:18Next Early Version
- 26:33Gregor Hardman
- 29:08Impact
- 31:04Security
- 32:49Micro Kernel
- 36:11Harmony OS
- 37:45Maintaining Open Source
related talks
57mPanel Discussion: Super Long Term Kernel Maintenance
30mKeynote: Dirk Hohndel, VP, VMware, in Conversation with Linux Creator Linus Torvalds
41mIs Linux Kernel Development Good Enough to Make Your Life Depend on It?
09mAspects of Dependable Linux Systems
36mNo, It's (Still) Never Too Late to Upstream Your Legacy Linux Based Platforms
25m[PATCH v22] Landing a Large Series
41mBoF: Embedded Linux Ecosystem
47mReal-Time Linux: What Is Next?