Kent Overstreet is the bcachefs maintainer and he's extremely pro-Rust. He has in fact talked about wanting to move bcachefs to Rust, and the userspace tools for bcachefs are already written in Rust.
He's been participating in the mailing list discussions about using Rust / providing Rust APIs for the FS subsystem.
I don't know who you're confusing him with, but you're confusing him with someone else.
Is Kent an unwilling pawn in the game of getting Rust implemented in the Linux kernel? Or is he not serious enough about getting it in that his support should not be considered?
From what I've seen it reads to me Kent would be very happy to implement bcachefs in Rust in the Linux kernel. Bcachefs-tools does make use of it.
Neither. In fact, Kent is the only person in this story that has any agency with respect to Linux whatsoever; he's the reason we're having this conversation in the first place. And indeed, this is also the reason Rust people wish to co-opt him so hard. This pattern of behaviour is not new; in fact, pretty much all "revolutionary" movements never pass on the chance to mistake good attitude (towards them) for unequivocal alliance in "the fight."
I like Rust in theory as much as the next guy, and the code is great, for one I think the kernel developers' concerns are slightly misplaced, but in practice I wouldn't want Rust people anywhere near my machines. Linux is a pretty old, and subpar operating system; it takes a great deal of effort to execute on it & only a handful of distributions (Debian) manage to get it right in the first place! Why don't they go for some other OS? There's Plan 9, there's Fuchsia, it's not like Linux is the only path forward. But they don't want to be writing file systems; instead, the only goal that matters to them is getting to the heart of the most popular OS, so as to secure some longterm success.
It all stems from insecurity, if you ask me.
Wrong final word: security. In the war against remote exploits, harden the most widely used target first.
Rust only exists because getting people to reliably and consistently write secure C++ proved impossible.
(yes I know C++ is a much larger and more complicated language than C)
If the Linux community was serious about, and not just cheap + ignorant, we wouldn't be having this conversation in the first place. Pandering programming language-equivalent of condom ads to this very community is not a sign of smarts, or great aspiration, but cluelessness and naivety.
> ECC memory
This is entirely Intel's fault.
From a quick search, I've found that the person is somewhat active in kernel commits over the last four years (mostly but not all rust related from what I see) and is involved in some lkml stuff and some commits over a decade ago. Not sure if this makes him a newcomer or not, just wanted to provide a bit more context.
Not in this case. It's the Rust evangelist who is the newcomer. FTA:
> Almeida said that he is not trying to keep the C API static; his goal is to get the filesystem developers to explain the semantics of the API so that they can be encoded into Rust.
The responses from the kernel team members to the proposal seem reasoned and mature to me:
> In addition, when the C code changes, the Rust code needs to follow along, but who is going to do that work?
> As the C code evolves, which will happen more quickly than with the Rust code, at least initially, there will be a need to keep the two APIs in sync.
> The object lifecycles are being encoded into the Rust API, but there is no equivalent of that in C; if someone changes the lifecycle of the object on one side, the other will have bugs.
> Encoding a single lifecycle understanding into the API means that its functions will not work for some filesystems.
> Part of the problem, Ted Ts'o said, is that there is an effort to get "everyone to switch over to the religion" of Rust; that will not happen, he said, because there are 50+ different filesystems in Linux that will not be instantaneously converted.
> Bottomley said that as more of those semantics get encoded into the bindings, they will become more fragile from a synchronization standpoint
> But Ts'o pointedly said that not everyone will learn Rust; if he makes a change, he will fix all of the affected C code, but, "because I don't know Rust, I am not going to fix the Rust bindings, sorry".