Linux 7.0 is in release candidates, and Rust is staying

Linus Torvalds confirmed in February that the kernel after 6.19 would be numbered 7.0, per Phoronix's report, and the release-candidate series has been proceeding on schedule, rc5 arriving in late March with the stable release expected mid-April. Torvalds' own framing: the version bump is bookkeeping, not revolution. The 6.x era simply ran out of digits he liked.

The substantive line in the release notes is about a language. With this cycle, Rust support in the kernel is no longer marked experimental: a permanent part of kernel infrastructure, in a codebase that was C and only C for three decades. The experiment label was doing real work while it lasted, letting skeptics treat the whole effort as reversible. Removing it is the project saying, in its own procedural dialect, that the argument is over.

It is worth remembering how unlikely this looked. Kernel culture resists dependencies, resists toolchain churn, and resisted this loudly; the mailing-list battles were public and occasionally theatrical. What settled it was not advocacy but attrition of the alternative: memory-safety bugs kept arriving on schedule, and the drivers written in Rust kept not producing them.

The builder's read: nothing changes for userland on day one, and that is the point. The kernel just demonstrated how a forty-million-line C project adopts a second language: slowly, in drivers first, behind a label it removes only when removal is boring. Any organization nursing a legacy codebase has just been handed the reference migration, at production scale, for free.