News for hackers. Stuff that matters.
Re:Klint: Compile-Time Detection of Atomic Context Violation... by PaulDavisThe1st on Sunday March 19, 2023 @12:14AM (#35215970)
I don't know of any bespoke solutions in the kernel that belong in a language.

RCU does not belong in a language. Spinlocks do not belong in a language. etc. etc.

These are things that belong in libraries/modules, which leads me to think that there's absolutely zero need for a (linux) kernel specific language.

Re:Klint: Compile-Time Detection of Atomic Context Violation... by tialaramex on Sunday March 19, 2023 @08:49AM (#35218438)
The kernel's extended BPF is in fact an entire virtual machine and so necessarily has a virtual machine language. Arguably it would be better if that software was written in a language intended to be translated into eBPF rather than in C, C++ or Rust compiled for the eBPF virtual machine.

EtA: Also, while the kernel does have some mechanisms which exist elsewhere, the kernel also has its own memory model, distinct from the C++ (and eventually C) memory model, because Linux has been here a long time and needed a model before C++ had one. So this means there's a conflict between what the ISO document says (based on its memory model) and how Linux works (based on its memory model).

So it might be easier on folks if the Linux memory model wasn't just a different memory model for the C language which already has a memory model. That applies just as well for Rust.