Linus Torvalds had already said it before: the Linux kernel is not a “social justice” project. But his latest overnight message adds a decisive piece: Linux won’t be an anti-AI fortress either. In a sharp reply on the mailing list, the kernel’s creator reaffirmed that using Large Language Models in kernel development should not be fought on principle, and he pushed back against developers who want to ban any AI-generated or AI-assisted contributions.

The trigger was a wave of hostility from some contributors toward the use of LLMs for writing patches or technical discussions. Torvalds didn’t mince words: blanket rejection makes no sense if contributions are evaluated by the same criteria as always. The issue isn’t the tool, but the result. “We are not a social movement. We are not anti-AI,” he wrote, shutting down any attempt to turn the kernel into an ideological trench.

Beneath the exchange lies a tension that runs through all critical software infrastructure. For months, maintainers of large open-source projects have been receiving LLM-generated patches that are syntactically clean but hollow in substance or riddled with subtle errors. The fear is pollution of the contribution stream: a flood of bot-produced code that risks drowning human reviewers, raising the noise floor and lowering quality unless filtered ruthlessly.

Torvalds opts for the pragmatic route. Instead of putting up barriers, the kernel will keep judging patches by their shoulders: do they work or not, are they safe or not, do they meet standards or not. It’s the same stance the project has always held toward anonymous contributions or code from companies with ulterior motives. The burden of proof rests on the reviewer, not the producer.

This doesn’t eliminate the risks. The kernel is a machine where a single bug can become a planet-wide security vulnerability. LLM-generated code might introduce known patterns linked in unexpected ways to race conditions that are hard to spot with a superficial read. The bet is that maintainers, subsystem leads, and top-level integrators will have the discipline to reject anything that doesn’t show profound understanding by its proposer — a level of competence that no model, however large, can fake.

Then there’s the legal dimension. Automatic generation raises unresolved copyright questions, especially for code covered by the GPLv2 license that the kernel has no intention of abandoning. If a patch comes from an LLM trained on repositories with mixed licenses, the authorship and license compatibility become murky. Torvalds didn’t directly address this point, but his “no technical shortcuts” line implies that such ambiguities will be handled case by case, without ideological prejudice.

For environments where data sovereignty is central — from on-premise appliances to air-gapped systems — the stance carries an indirect reflection. Locally run AI-assisted development tools could speed up porting and custom kernel maintenance. But the quality guarantee doesn’t come from automation; it comes from the human review process. Torvalds’ message reinforces the idea that technical integrity remains the ultimate filter, without yielding to temptations of convenience.

In the end, the kernel doesn’t turn into a lab for unleashing LLMs unchecked, but it doesn’t lock itself in a pre-AI ivory tower either. It’s a choice that spices a debate destined to run: can open-source communities withstand the pressure to produce code faster using AI while keeping quality and openness intact? Linux answers no, if withstanding means building a wall. Instead, they’ll work overtime to tell value from noise.