Skip to content

Q003 — Linux Kernel Uses Bespoke CI; Others Unstudied — Reading List

Contents

Must Read

  • Kernel Testing Guide
  • Linux kernel documentation maintainers · Kernel v6.5 (2023)
  • Official Linux kernel documentation covering the testing tool ecosystem: KUnit for unit testing, kselftest for system testing, code coverage (gcov, KCOV), dynamic analysis (KASAN, UBSAN, KCSAN, KFENCE, lockdep), and static analysis (Sparse, Smatch, Coccinelle).
  • Why read: The authoritative primary source for kernel quality tooling — essential for accurately describing what the kernel actually uses rather than relying on third-party summaries.

Should Read

  • How is the Linux kernel tested?
  • Sergio Prado (Embedded Bits) · October 23, 2021
  • Comprehensive overview of Linux kernel testing infrastructure: static analysis (Sparse, Smatch, Coccinelle), test automation (ktest, kselftest, LTP, Autotest, KUnit), fuzzing (Trinity, Syzkaller/Syzbot), and CI systems (KernelCI, Intel 0-Day Test Service, LKFT).
  • Why read: The most accessible and comprehensive single overview of kernel testing infrastructure — useful as a narrative complement to the official docs for readers unfamiliar with kernel development.

Reference

  • CNCF Hosted Tools and Services
  • CNCF (Cloud Native Computing Foundation)
  • CNCF documentation stating that the foundation covers CI needs for hosted projects and allows projects to select their own CI platforms.
  • Why read: Documents the CNCF infrastructure model — relevant for understanding that even foundation-backed projects are not mandated to use specific security scanning tools.

← Back to item overview