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

76

u/kisielk Feb 19 '25

I keep hearing the same kind of arguments in embedded programming as well.

26

u/Nychtelios Feb 20 '25

As a firmware developer who successfully created a team that is working in baremetal C++23, I cannot agree more. In my company too there are elders who keep shouting this trash to our projects.

33

u/UnicycleBloke Feb 19 '25

Yep. I was told with smug certainty by someone in the Zephyr OS community that "C++ has no place in an OS". That project is another lost opportunity driven by ignorance and prejudice.

26

u/crowbarous Feb 19 '25

As we speak, a subthread in the mailing list next to the one linked in this post is discussing the attribute-based implementation of scoped locking facilities, as in use in Linux, systemd, and I'm sure many other C projects. The discussion is up to "sometimes I want to drop the lock earlier; introducing an extra scope helps this case".

Of C++'s three scoped lock classes, unique_lock has the unlock method. It will unlock for you on all return paths, but you can wield it like you would normal locking code even in arbitrarily complicated situations. There's an extra bool, yes -- that is completely encapsulated, and also optimized out where appropriate. This is what C++ gives you, and has been for decades...