Panel Discussion: What is Lacking in Linux Security and What Are or Should We be Doing about This
summary
Calls for treating testing as core: integrate static analysis, unify test formats and crash reporting, and require regression tests for fixes because sisbot found thousands of bugs and releases carry tens of thousands of patches. Propose reducing defects per release by orders of magnitude, adopt hardware-assisted sanitizers (MTE) and probabilistic sampling ASAN for production, and fix benign data races so KCSAN can run. Also push for better exploit-aware reviews and per-patch self-tests to help overloaded maintainers.
AI-written summary · about
chapters (4)
related talks
27mSecurity: The Thing That Everyone...
06mQ&A
45mLooking at Linux as a SEooC
21mFrom CVEs To Compliance: Automating Embedded Linux Kernel Security
02mSafe Systems with Linux MC Wrap up and next steps
37mBringing Security to Your Open Source Project
28mKeynote: Window Snyder, Chief Software Security Officer, Intel in conversation with Jim Zemlin
01h 01mSoftware Security
