Rust is part of mainline Linux, but the available upstream documentation does not establish a general-purpose async runtime or a supported async Rust driver API for in-kernel code. Rust’s async and await syntax alone does not supply the executor needed to run futures. The key distinction is between Rust language support in the kernel and an async execution model supported by a particular kernel subsystem.
What does async Rust support in Linux mean?
There are two separate questions: can kernel code be written in Rust, and does the kernel provide a supported way to execute Rust futures asynchronously? The first is established: Rust support entered mainline Linux in version 6.1, and the kernel’s Rust documentation describes work on abstractions, drivers, infrastructure, and tools. The second is not established by the upstream sources cited here.
As an Amazon Associate I earn from qualifying purchases.
In ordinary Rust programs, async defines a future and await suspends its execution until an executor drives that future to completion. The Rust API reference explains that dependency, but does not confirm that an executor is supplied for in-kernel Rust code. Language-level async syntax should therefore not be mistaken for a kernel runtime or driver framework.
How does the documented Rust driver model work?
The generated kernel Rust API documentation describes a bus-specific Driver trait and a registration model. That is evidence of a driver interface for the documented bus, not a universal async driver API. Whether a driver can use asynchronous operations depends on the interfaces and execution facilities provided by its subsystem.
#1 Best Overall
Linux’s Rust adoption is managed through ordinary subsystem ownership. The Rust for Linux policy says individual subsystems can choose how to adopt Rust or defer it; the RUST subsystem owns selected core facilities, not every Rust component. Consequently, a claim about async support needs to be tied to a specific subsystem and its current upstream API rather than inferred from Rust integration alone.
What is the current project status?
In a presentation at Linux Plumbers Conference 2025, Rust for Linux maintainer Miguel Ojeda said, “But the experiment is done, i.e. Rust is here to stay.” This referred to the maintainers’ conclusion of the Rust experiment, not the end of development or a guarantee that every configuration works. Ojeda also cautioned that configurations, architectures, and toolchains were not uniformly supported, with continuing work across the kernel, Rust, GCC, and other projects. LPC 2025 presentation
Rank #2
Toolchain work remains part of the effort. The Rust Project’s 2026–2027 goal concerns stabilizing compiler features required by Linux, including areas such as architecture flags, sanitizers, mitigations, and optimization features. Its 2026 roadmap also lists “Guaranteed destructors” as an exploration for 2026–2027 that could enable patterns such as safe scoped spawning for async. These are future language and compiler goals, not proof of a current in-kernel async API.
Free tools Windows power users keep installed
One-click scans. No signup required.
What can developers conclude before building a driver?
- Rust in mainline is real: support entered in Linux 6.1, but this alone does not imply async execution support.
- Check the target subsystem: determine whether its upstream Rust interfaces provide the operations and execution model your driver needs.
- Do not infer an executor from
await: futures need an executor to be driven, and the cited API reference does not establish an in-kernel one. - Check version and toolchain constraints: Rust kernel development continues to involve compatibility and compiler-feature work; support can vary by configuration, architecture, and toolchain.
For primary references, see the Linux 6.16 Rust documentation, the kernel Rust driver API documentation, the Rust await reference, and the Rust for Linux kernel policy. The roadmap details are in the Rust Project’s 2026 Rust for Linux roadmap and 2026–2027 compiler-features goal.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
