What Linus Torvalds Really Thinks About AI, Rust, and the Future of Linux Kernel Development

1. Linus Torvalds’ Evolving Role

After nearly 20 years of direct coding, Linus now functions primarily as a system‑level technical leader and maintainer for the Linux kernel and Git. He reviews patches, makes high‑level architectural decisions, and delegates most implementation work to the broader community. He emphasizes that real contributions come from other developers and that his daily activity is largely observing the kernel’s progress.

2. Rust’s Integration into the Kernel

Rust has been present in the kernel for roughly three years, but its full adoption took longer than expected. Linus acknowledges that Rust is now a genuine part of the kernel codebase rather than an experimental side‑project. The language’s inclusion has sparked debate, but it is considered valuable for attracting new contributors and for writing safer subsystems. The effort to make Rust a first‑class language has required more time and coordination than initially anticipated.

3. Hardware Trends: GPUs and AI Workloads

The rise of Nvidia and AMD GPUs, together with AI‑driven workloads, has increased the importance of accelerator support in Linux. Linus notes that the kernel’s core responsibilities—system stability, resource management, and hardware abstraction—remain unchanged, but the kernel now interacts more heavily with GPU drivers and virtual memory management to accommodate AI workloads. Nvidia’s recent interest in Linux is seen as a positive side effect of AI’s growth in the cloud.

4. AI in Kernel Development

AI tools are still largely experimental for kernel work. Current experiments include using AI to triage patches, back‑port fixes, and generate code suggestions. Linus reports that AI‑generated security reports of low quality have begun to consume maintainer time, and aggressive crawling of kernel.org by AI bots creates bandwidth and indexing issues. He views AI as a productivity tool comparable to compilers: it can automate repetitive tasks but will not replace developers.

5. Recent Kernel Release (6.18 RC4)

Linus described the 6.18 release candidate as “boring” in the sense that it does not introduce disruptive new features that could destabilize millions of systems. Test failures observed were mostly due to the test infrastructure rather than kernel regressions. The release is progressing incrementally and is considered stable for the upcoming final release.

6. Communication Practices

Linus reads a large volume of email daily but replies only when necessary. He explains that a lack of response usually indicates satisfaction with the submitted work rather than neglect. He apologizes for the perception of being unresponsive, emphasizing that his silence is not meant to be hostile.