Linux Kernel Testing: Providing Better Results to the Upstream Community
summary
Three new kselftests target probe regressions: a device-tree probe kselftest and an ACPI probe kselftest that iterate platform nodes and check sysfs (CFS) driver folders, plus a third that uses a per-board YAML binding for discoverable devices kept out of tree. Tests land in mainline (available since 6.8), use KtAP-compliant output, run in a lab of 200+ devices under the rebuilt kernel CI, and already triggered multiple upstream patches that fixed real regressions and reduced false negatives.
AI-written summary · about
chapters (21)
- 0:00Linux kernel testing intro
- 1:04Testing quality in the kernel
- 2:50Kosci CI system challenges
- 4:18False negatives in CI
- 6:24Legacy device probe problems
- 7:28High-quality kernel tests
- 9:13Prioritizing in-tree tests
- 10:17Analyzing failures to improve
- 11:24Device probe KUnit tests
- 13:30Device Tree probe tests
- 15:15ACPI probe tests and pitfalls
- 17:42Edge cases in ACPI probing
- 19:28Testing dynamically discovered devices
- 21:17Kernel testing limitations
- 22:42Fixing KUnit output conformance
- 23:52Expanding test coverage
- 24:55Machine-readable kernel errors
- 25:57Plans for new KCI system
- 26:40Community engagement
- 27:46Recap and call for involvement
- 28:30Q&A
related talks
34mLinux Kernel Testing: Providing Better Results to the Upstream Community
19mChecking your work: Linux kernel testing and CI
23mExperiences and lessons we learned using kselftest and pote
35mDetecting failed device probes
16mKselftests augmented: running kernelspace tests from userspace
30mKernel Testing with KUnit: Bridging the Gap
41mKeeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices
39mDay-to-day Testing of Linux 'Next' Kernel Branch - My Story