Linux team approves new terminology to replace terms like “master/slave” and “blacklist/whitelist” for new Linux kernel source code and associated documentation
Linux creator Linus Torvalds puts stamp on proposal to use neutral language in kernel code and documentation.
Context & Ripple Effects
This closes the loop on the terminology push that began after the industry-wide movement to replace whitelist/blacklist and master/slave terms surfaced in June amid protests. Apple had already moved days earlier, updating its Style Guide to deny list/allow list and main branch — but the Linux kernel is the higher-stakes adoption because its source code, not just documentation, is affected.
The approval also lands differently because of who signed off: Linus Torvalds, whose 2018 step-away over the Code of Conduct controversy and subsequent return under the new Linux 4.19 conduct framework made him the sector's most-watched holdout on community-norm changes.
First-order effects
- Contributors submitting new kernel code and documentation now have an enforced naming convention — patches using master/slave or blacklist/whitelist terminology face rejection at review, shifting the burden onto thousands of active kernel developers rather than a single maintainer.
- Torvalds' endorsement converts what was a per-project style choice into de facto policy for the largest open-source codebase, giving proponents of neutral terminology their most credible reference case.
Second-order effects
- Other major projects that were waiting on a signal now face pressure to match Apple's Style Guide change and the kernel's decision, since divergent terminology across codebases raises friction for developers and tooling that span both.
- Vendors shipping Linux-based products inherit the convention through their downstream trees, so enterprise distributors' documentation and interfaces will drift toward the same terms without separate decisions of their own.
Third-order effects
- If the pattern holds, inclusive-language rules become a standing component of open-source governance — codified alongside codes of conduct rather than debated ad hoc each time — making terminology a routine review criterion like licensing or style compliance.
- The episode marks the point where community norms set by the largest foundations propagate top-down through dependent ecosystems, reversing the older assumption that kernel culture was insulated from broader corporate and social pressure.
The trend: Inclusive terminology is moving from isolated corporate style guides to enforced conventions in foundational open-source infrastructure, with the Linux kernel's approval setting the standard other projects now measure against.