[PATCH v22] Landing a Large Series
summary
Seven years of work refactors Linux security modules from a single-user design into a multi-module stack, culminating in [PATCH v22] and many incremental patch sets (objective threshold: >15 patches or >300KB). Development habitually spends ~20% of time rebasing; reviews iterate across networking, audit, VFS and security subsystems. Series breaks into staged wins—first enabling run AppArmor and SELinux concurrently, then broader integration—code that finally lands often looks very different from the original plan. LSM stacking
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:53What is a Large Series
- 1:33Large Series Examples
- 2:36Why Its Hard to Do a Large Series
- 3:49What to Do
- 5:16Incremental Stages
- 7:36Documentation
- 9:50Respect and Engage
- 13:00Unnecessary Changes
- 13:46Lobbying
- 14:16Who
- 15:34Enemies
- 18:07Learning
- 20:08Stalls
- 22:41Giving in
related talks
46m20 years of NSA Security Enhanced Linux, a Retrospective
33mSecurity Module Stacks That Don't Fall Over
17mSustaining Yesterday’s Linux: Delivering Security for Today’s Workloads
15mSubsystem Update: LSM Stacking - What You Can Do Now and What's Next
30mLSM Stacking - What You Can Do Now and What's Next
36mLinux Kernel Developer Panel
30mSecurity Module Stacks that Don't Fall Over
23mOverview and Recent Developments: seccomp and Small Linux Security Modules