Why Linus Torvalds Is Blocking Rust Drivers in the Linux Kernel

Another Linux kernel controversy has erupted, this time over Rust device drivers, with Linus Torvalds delivering a decisive rebuke.

Responding to Asahi Linux lead Hector Martin’s appeal, Torvalds dismissed Martin’s defense that social‑media attacks were justified, instead directing criticism at Martin himself.

Torvalds admitted difficulty handling diplomatic disputes, stating, “Accept the fact that the problem may lie with you; you think you know better, but the current process works.”

He added, “The issue exists, but it’s a fact of life—nothing is perfect.”

Torvalds emphasized that social‑media attacks make him unwilling to engage, arguing that if the core development model is flawed, social media is not the solution, just as it cannot solve political problems.

He stressed the importance of technical patches and discussion over publicity.

Torvalds’ restrained remarks echo Apple’s silence warnings to developers; he warned that media attacks are useless, yet his stance faced strong opposition.

Martin later requested removal from upstream Linux code maintenance for Apple‑compatible ARM hardware.

After a clash with kernel maintainer Christoph Hellwig, Martin was accused of “inciting” community sentiment on social media. The dispute stems from Hellwig’s opposition to a patch allowing Rust drivers to call the core DMA API, which allocates and maps memory for direct memory access.

The Linux kernel is primarily written in C. In recent years, C and C++ have waned as manual memory‑management languages lead to safety bugs with severe security consequences.

Rust, a newer language, aims to enhance memory safety through its ownership model, preventing many common vulnerabilities found in C and C++. Consequently, Rust is promoted as a way to reduce memory‑safety issues in software development.

The Linux kernel team began integrating Rust code in 2022, but the codebase remains C‑centric. Many C contributors have stated they will not change their coding practices because of Rust’s rise.

Tensions between C and Rust developers arise from Rust’s memory‑safety features being introduced into a traditionally C‑dominated codebase, with some maintainers resisting added complexity and potential maintenance burden.

Hellwig’s firm rejection of the patch led Martin to urge the Rust‑for‑Linux team to merge the series promptly after review, ignoring Hellwig’s obstruction.

Martin later posted a message urging avoidance of the “in‑house drama,” which was later deleted after Torvalds exercised his final authority over driver patches.

He wrote, “Either Linus likes it or hates it; everything else is sabotage by a group of disruptive maintainers trying to demoralize you until you quit, knowing they’ll eventually become history’s failures.”

Despite this, resistance to Rust among kernel maintainers may slow the community’s reform, leaving the fate of Rust patches uncertain.