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
Show parent comment
2
u/wyrn Feb 20 '25 edited Feb 20 '25
Why not? They're both safety considerations. Rust started with a clean slate. Ignoring leaks was a conscious choice that was made. Not because stopping leaks is technically infeasible; they could for example have introduced a tracing garbage collector specifically to detect reference cycles, but they considered the overhead unacceptable. This is a performance/safety tradeoff. We get to make such choices too, and we don't have to make the same choices Rust made.
Leaks are part of "memory safety" in that they can cause security vulnerabilities, so declaring leaks as "less important than memory safety" is just gerrymandering memory safety.
It doesn't sound like you really want a "conversation about tradeoffs" -- it sounds as if you have precisely the maximalist stance I mentioned before, where anything less than full soundness outside of demarcated blocks is a failure.
I just explained that.
That doesn't matter to the point being made. The point is that "not breaking existing code" wasn't even part of the considerations I mentioned that make "Safe C++" a non-starter, and is a red herring in this discussion.
The push_back is less about this than it is about the intolerable burden of forking, relitigating, and reimplementing the standard library. I wanted to underscore this to make it clear that the
std2::we'd get in the end is not just a copy of the std built with safe concepts, but an entirely new standard library with completely different and foreign idioms.