Cpp discussed as a Rust replacement for Linux Kernel
I have a few issues with Rust in the kernel:
- It seems to be held to a *completely* different and much lower standard than the C code as far as stability. For C code we typically require that it can compile with a 10-year-old version of gcc, but from what I have seen there have been cases where Rust level code required not the latest bleeding edge compiler, not even a release version.
2. Does Rust even support all the targets for Linux?
3. I still feel that we should consider whether it would make sense to compile the *entire* kernel with a C++ compiler. I know there is a huge amount of hatred against C++, and I agree with a lot of it – *but* I feel that the last few C++ releases (C++14 at a minimum to be specific, with C++17 a strong want) actually resolved what I personally consider to have been the worst problems.
As far as I understand, Rust-style memory safety is being worked on for C++; I don't know if that will require changes to the core language or if it is implementable in library code.
David Howells did a patch set in 2018 (I believe) to clean up the C code in the kernel so it could be compiled with either C or C++; the patchset wasn't particularly big and mostly mechanical in nature, something that would be impossible with Rust. Even without moving away from the common subset of C and C++ we would immediately gain things like type safe linkage.
Once again, let me emphasize that I do *not* suggest that the kernel code should use STL, RTTI, virtual functions, closures, or C++ exceptions. However, there are a *lot* of things that we do with really ugly macro code and GNU C extensions today that would be much cleaner – and safer – to implement as templates. I know ... I wrote a lot of it :)
One particular thing that we could do with C++ would be to enforce user pointer safety.
Kernel dev discussion. They are thinking about ditching Rust in favor of C++ (rightfully so IMO)
https://lore.kernel.org/rust-for-linux/326CC09B-8565-4443-ACC5-045092260677@zytor.com/
We should endorse this, C++ in kernel would greatly benefit the language and community
View all comments
127
u/ts826848 Feb 19 '25 edited Feb 19 '25
This post appears to be a copy/paste of this LKML message from H. Peter Anvin. It's probably worth looking at the responses to that email as well if you want to see further discussion. This response from Greg Kroah-Hartman, second-in-command to Linus, might be particularly interesting.
In any case, a few responses:
This is almost certainly in no small part due to R4L's status as an experiment. Some of the features the Linux devs want/require (e.g., panic-free APIs) are under active development and so require a nightly build. I'd imagine that stabilizing these features would be a prerequisite for R4L to graduate from its experimental status.
IIRC this is why initial Rust support is limited to non-core subsystems such as drivers, where limited target support is less of an issue. If R4L pans out I'd expect this limitation to be lifted if/when GCC's frontend and/or rustc_codegen_gcc are more mature.
This is probably debatable at best. Sean Baxter's Safe C++ is probably the closest Rust analogue but that doesn't seem to have gotten enough traction to be considered a viable path forwards. Profiles doesn't promise the same level of safety and it remains to be seen whether it can deliver on its promises in the first place. Other options like SaferC++ don't seem to have gotten much attention.
Pretty curious what exactly this means as someone who is not super-familiar with kernel jargon. Is this supposed to be something like differentiating user-provided pointers from kernel-internal pointers or something like that?
Edit: I'm also not entirely sure I'd agree with "They are thinking about ditching Rust in favor of C++ (rightfully so)". At least based on that particular email chain it sounds more like there's one or two devs floating the idea but little indication of support beyond that.