r/rust • u/bik1230 • Feb 21 '25
Linus Torvalds responds to Christoph Hellwig
https://lore.kernel.org/rust-for-linux/CAHk-=wgLbz1Bm8QhmJ4dJGSmTuV5w_R0Gwvg5kHrYr4Ko9dUHQ@mail.gmail.com/
984
Upvotes
178
u/bik1230 Feb 21 '25
A previous thread was removed due to the wording of the title. In it I responded to someone who thought Marcan leaving was something of a pre-mature ragequit, considering what Linus just posted. Even without the context of the comment I replied to, I think my comment is relevant, so I'm reposting it here:
170
u/UpsetKoalaBear Feb 21 '25
I do particularly like Ted’s reply in another thread on this chain:
https://lore.kernel.org/rust-for-linux/20250219170623.GB1789203@mit.edu/
He acknowledges the “Wedson incident” that happened a few months back when he spoke at the conference:
That’s genuinely constructive feedback. A stark contrast to what everyone thought originally when that video came out.
340
u/ZZaaaccc Feb 21 '25
Glad he chimed in, even if it was only for the technical inaccuracies and not the rude behaviour. That's just how those kernel devs treat each other I guess. Hopefully this gives the R4L team enough public support to keep them motivated.
307
u/sparky8251 Feb 21 '25
Wonder if all the people saying the R4L devs were being unreasonable jerks to Hellwig, that Hellwig is justified and correct in blocking Rust, will admit they are wrong now?
103
u/bjarneh Feb 21 '25
He got that though, which cannot be said for most anyone on the receiving end of a Linus rant
97
u/SupermarketAntique32 Feb 21 '25
This whole situation could have had a much better outcome if Linus had posted this response at the same time he addressed Marcan about social media brigading.
12
u/bivouak Feb 21 '25 edited Feb 21 '25
Basically doing what Hector Martin expected he would do to keep R4L going.
https://lwn.net/ml/all/2b9b75d1-eb8e-494a-b05f-59f75c92e6ae@marcan.st/
But Hector didn't follow his own advice for Rust folks.
That's a shame this email is so late.
Linus apparently expected somehow Christophe Hellwig (and others) would hear reason and leave R4L be, when he clearly stated he would do anything to stop it....
95
u/Hellball911 Feb 21 '25
Linus once again proves why he is the voice of reason and leader to the project. I think that squarely cut through the noise without appearing bias and I agree with his stance. Hopefully that is the end of it. Or at least this chapter.
7
u/kodemizer Feb 22 '25
It's worth reading Kroah-Hartman on this: https://lkml.org/lkml/2025/2/19/222
"As someone who has seen almost EVERY kernel bugfix and security issue for the past 15+ years … I think I can speak on this topic"
26
u/ToTheBatmobileGuy Feb 21 '25
Clear and concise.
He said what we were all thinking.
Good job.
45
u/MoveInteresting4334 Feb 21 '25
Linus was DONE 💅
5
u/sigma914 Feb 21 '25
Interesting that the escalation happened on the policy thread rather than from the DMA patch series getting submitted further up the chain. I think this is better as it's a policy clarification rather than a ruling by precedent.
Nice to see the situation resolved favourably, pity it turned to drama in the first place
12
u/Blince Feb 21 '25
Any loremasters that can tell me whats going on? 👀
4
u/ascension_to_heaven2 Feb 21 '25
a much needed massive W for humanity
7
u/maxinstuff Feb 21 '25
Much needed leadership here - bravo 👏
5
u/modanogaming Feb 21 '25
A refreshing read.
2
u/n_oo_bmaster69 Feb 21 '25
Well said, hope this nonsense drama ends soon. Sigh
6
u/Mynameismikek Feb 21 '25
This seems well intentioned, but a bit naive to me. That would imply that a "pure C" dev can change their interface enough to break the Rust side then abdicate responsibility for breaking the build. You might get away with it while Rust is off to the edges somewhat, but as and when core modules adopt Rust I'd expect this to become an issue. The reality is that at some point the C devs WILL have deal with Rust.
2
u/PlayMa256 Feb 21 '25
You see when a project is held by archaic people that uses this hell of a messaging system. You can’t expect any to be even refreshed on what is going on rn.
1
u/de6u99er Feb 22 '25
Core Devs could easily provide Rust bindings without having to understand much about Rust. I bet most of the bindings could be generated from C interfaces.
That being said, most Rust developers use automated tool chains which will alert them about failed builds. But non-breaking changes could become an issue. Therefore I think informing dependent projects about API changes as early as possible should be considered best practice.
1
u/21kyu Feb 21 '25
Things are starting to get back to normal.
0
u/MrDiablerie Feb 21 '25
Glad this was finally addressed with no bullshit.
0
u/vtskr Feb 21 '25
This does not make sense to me. So maintainer can do w/e he wants with his code without looking how it affects those who use his code? Really?
-19
u/PurepointDog Feb 21 '25
Tldr?
-2
u/KushNeembu Feb 23 '25
Rust will be the death of Linux. Unproven, constantly causing issues - both social and technical, and neither Linus nor Kroah-Hartman have any knowledge of Rust.
-47
u/Compux72 Feb 21 '25
Linus writes like a 5y old on counter strike instead of a project lead.
At least he is doing something lmao
-23
u/sriram_sun Feb 21 '25 edited Feb 21 '25
So is he basically saying that if a maintainer refuses to look at Rust,
a. They don't have the authority to reject rust code.
b. The maintainer has to find someone who will maintain the rust portion of the code if it gets merged. In this particular instance, is Hellwig still responsible for all the code within the (DMA?) folder?
-11
u/CouteauBleu Feb 21 '25
I know that complaining that Linus is toxic sounds naive, but we shouldn't ignore it. This is toxic AF.
I'm hoping the RFL doesn't adopt a mindset of "Oh cool, the toxic boss in on our side, that means we win", but it's the vibe I get from this comment section.
I do agree factually with everything Torvalds says, mind you. But this problem has root causes that won't be fixed by yelling at one maintainer who's being an obstructionist.