[go: up one dir, main page]

|
|
Log in / Subscribe / Register

Committing to Rust for kernel code

Committing to Rust for kernel code

Posted Nov 25, 2023 8:02 UTC (Sat) by marcan (guest, #103032)
In reply to: Committing to Rust for kernel code by ojeda
Parent article: Committing to Rust for kernel code

Hey Miguel,

I just opened a thread on the Zulip to talk about this. Conan doesn't have too much visibility into the actual work going into our downstream branch Rust support, but I do. And indeed, the biggest problem is 100% upstream: it's the `alloc` crate. That's what is breaking with almost every compiler version bump, and I haven't seen any discussion or plans for how that will be resolved yet.

Upstreaming, the small handful of features used in the other crates, etc. are all things with solid plans going forward, and I look forward to the future for Rust for Linux. But as long as `alloc` is using 100+ unstable features directly upstream, all the work to eventually drop the dozen features used in the `kernel` crate is rather useless. Being able to unpin the Rust compiler version is very important for distros to start taking this seriously and reduce friction enabling Rust support, so I hope there is some plan to eventually solve this. Maybe there is and I just haven't found it? Would be happy to hear your thoughts :)


to post comments

Committing to Rust for kernel code

Posted Nov 25, 2023 15:44 UTC (Sat) by ojeda (subscriber, #143370) [Link]

The alloc topic has been in discussion since essentially the beginning of the project. The original plan discussed with upstream Rust (and others) is documented in-tree, please see the rust/alloc/README.md file. In short, the alloc fork is meant to be temporary and the discussions with upstream Rust are ongoing.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds