New Linux Patch Confirms: Rust Experiment Is Done, Rust Is Here To Stay

Miguel Ojeda, lead developer for Rust for Linux, posted a patch to remove the “Rust experiment” designation from kernel documentation after the Linux Kernel Maintainers Summit, declaring that Rust’s trial phase is concluded; Rust support was originally merged in v6.1 and is already used in production, enabled by some distributions and present in millions of Android devices. The Rust code is not yet built by default and certain configurations—such as mixed GCC+LLVM builds and forthcoming GCC support—remain experimental, but the change is intended to signal long-term commitment and encourage companies to invest in training and development. As Rust-written drivers (for example the open-source NVIDIA Nova driver) and other modern drivers mature, broader adoption and eventual default inclusion are likely, although substantial work on the kernel, Rust itself and compiler toolchains remains.

Analysis

Miguel Ojeda, the Rust for Linux lead developer, posted a patch after the Linux Kernel Maintainers Summit and the Linux Plumbers Conference to remove the "Rust experiment" designation from kernel documentation, formally declaring that the trial phase is concluded. Rust support was originally merged into mainline in v6.1 and Ojeda notes there are already production uses, with some well-known Linux distributions enabling Rust and presence in millions of Android devices.

The Rust kernel code is not yet built by default and several configurations remain experimental; mixed GCC+LLVM builds and the forthcoming GCC support are called out as work in progress. The message signals a shift from research to sustained development — Ojeda explicitly framed this as an invitation for companies to invest in training and long-term kernel Rust work.

Near-term adoption vectors include Rust-written modern drivers and the open-source NVIDIA (Nova) driver, which could drive de facto default inclusion if they become broadly useful to end users. Remaining risks are substantive: compatibility across architectures, toolchains and upstream projects (Rust, GCC, LLVM) still requires considerable engineering and could delay enterprise-grade adoption.

Key Decisions for Investors

• Monitor development milestones such as default build enablement and official GCC support as binary catalysts for broader adoption, reassess exposure when those milestones are reached
• Track vendor and distribution commitments to Rust kernel work—notably driver vendors like NVIDIA and major Linux distributions—since their adoption is the most direct near-term catalyst
• Consider selective exposure to ecosystem beneficiaries (tooling, compiler, security-audit services and cloud vendors supporting Rust workloads) but tranche investments to await clearer production-readiness signals
• Maintain caution and hedge technical-risk exposure until mixed GCC+LLVM and cross-architecture compatibility stabilize; use confirmed upstream defaults or widespread distribution enablement as triggers to scale positions