The Life of a Kernel Bugfix
summary
A kernel bugfix follows an upstream-first path: patch submitted to mainline with a Fixes: line and CC: stable triggers automatic backports and inclusion in weekly stable trees, then distros merge, QA and ship. Use git, the stable mailing list, and scripts/checkpatch.pl to validate commits; provide a reproducer and stack trace (often found by a fuzzer). Real examples show one patch getting cherry-picked back to 5.4 and into 6.6/6.12 stable releases, tested by CI and Linaro, then released to users.
AI-written summary · about
chapters (10)
- 0:00Kernel bugfix upstreaming intro
- 2:31Kernel release and stable process
- 7:42Distro vs upstream kernels
- 11:18Including fixes in distro kernels
- 15:53Mainline patch submission
- 21:42Stable kernel backporting
- 27:23Best practices for bugfixes
- 35:11Getting fixes into distro kernels
- 36:37Features versus bugfixes
- 38:44Q&A
