News for hackers. Stuff that matters.
Re:Committing to Rust in the Kernel by josephcsible on Tuesday September 24, 2024 @11:26PM (#41643416)
Why do we need quasi-stable anything within the kernel? Wouldn't a much better long-term solution be changing the rule to "break whatever APIs you want, but you have to fix all of the in-tree Rust uses too"?
Re:Committing to Rust in the Kernel by newpavlov on Tuesday September 24, 2024 @11:30PM (#41643444)
The problem is that some high-profile people who want to preserve their right to "break whatever", do not want to shoulder responsibility of fixing Rust code which depends on the broken stuff. Even worse, they even do not want to explain and document semantics of existing APIs (sic)! See the video linked in the sibling comment.

Speaking more broadly, freely breaking stuff in large projects is dangerous, since fixing stuff may require a more specialized expertise and knowledge, e.g. being well-versed in Rust safety rules, knowing some obscure information about hardware behavior, or being aware about some tricky invariant which must be preserved by the code. This is why changes in API boundaries often require synchronization between different teams.

Re:Committing to Rust in the Kernel by vlovich123 on Wednesday September 25, 2024 @12:41AM (#41643755)
At least Ted Tso has clarified his position greatly from what initially read as “I refuse to learn rust”. Instead yes asking for a guide to help him understand the Rust:

> There is a need for documentation and tutorials on how to write filesystem code in idiomatic Rust. He said that he has a lot to learn; he is willing to do that, but needs help on what to learn.

Re:Committing to Rust in the Kernel by steveklabnik on Wednesday September 25, 2024 @12:51AM (#41643803)
This is heartening to read for sure.
Re:Committing to Rust in the Kernel by pas on Wednesday September 25, 2024 @08:03AM (#41646391)
> since fixing stuff may require a more specialized expertise and knowledge

That's why sign-offs from reviewers are "required", no?

It seems the correct mentality to encourage people to do hack on the kernel, show that things are possible, they are "working on my machine", and then ... yeah, they will need to go through the usually length process of getting it merged.

But starting with "synchronization between different teams" usually gets shrugs and "let's get back to it soon"-s.

Re:Committing to Rust in the Kernel by arp242 on Wednesday September 25, 2024 @12:40PM (#41649246)
One of the advantage of big monorepos (and Linux really is just one big "monorepo") is that you can change $whatever as long as you also fix everything that depends on that.

Sometimes this is just simple stuff, like adding a function argument, changing a type, or something like that.

"Break whatever" is a bit of a crude way of putting it, but yeah, it's definitely an advantage IMHO. Not just for the final patch, but also prototyping, experimenting, showing ideas, etc.