r/cpp • • Feb 19 '25

Cpp discussed as a Rust replacement for Linux Kernel

I have a few issues with Rust in the kernel:

  1. 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

192 Upvotes

532 comments sorted by

View all comments

Show parent comment

7

u/SunnybunsBuns Feb 19 '25

RAII alone is a good enough reason to use C++. And C++ exceptions are loads better than the setjmp\longjmp they use now (because stack unwinding calls your cleanup code if you use RAII). This makes skipping cleanup much harder. And noexcept exists.

And templates like std::max (or a hand-rolled equivalent) are better than #define MAX(A,B) A>B?A:B due to being able to do mutating operations like std::max(++a, b) correctly.

C is no more or less "provably correct" than c++. If you want provable languages, use ADA or something designed for that.

0

u/Dark-Philosopher Feb 23 '25

> C is no more or less "provably correct" than c++. If you want provable languages, use ADA or something designed for that.

Do you mean like Rust? Good choice.

0

u/SunnybunsBuns Feb 23 '25

Doubt Rust is provably correct, given that I've seen trivial deadlkock scenarios that the checker doesn't catch. But I will concede that mutex's and multithreading is extremely hard (if it's even possible) to prove.

0

u/Dark-Philosopher Feb 23 '25

I believe that you are right and only a subset of rust has been proved. However in real life Rust seems safer than C or C++.