Wedson Almeida Filho is a Microsoft engineer who has been prolific in his contributions to the Rust for the Linux kernel code over the past several years. Wedson has worked on many Rust Linux kernel features and even did a experimental EXT2 file-system driver port to Rust. But he’s had enough and is now stepping away from the Rust for Linux efforts.

From Wedon’s post on the kernel mailing list:

I am retiring from the project. After almost 4 years, I find myself lacking the energy and enthusiasm I once had to respond to some of the nontechnical nonsense, so it’s best to leave it up to those who still have it in them.

…

I truly believe the future of kernels is with memory-safe languages. I am no visionary but if Linux doesn’t internalize this, I’m afraid some other kernel will do to it what it did to Unix.

Lastly, I’ll leave a small, 3min 30s, sample for context here: https://youtu.be/WiPp9YEBV0Q?t=1529 – and to reiterate, no one is trying force anyone else to learn Rust nor prevent refactorings of C code."

  • @[email protected]
    35•4 months ago

    I’m not insisting anything; stating C is not a memory-safe language isn’t a subjective opinion.

    Note I’m not even a Rust fan; I still prefer C because it’s what I know. But the kernel isn’t written by a bunch of Lewis Hamiltons; so many patches are from one-time contributors and the kernel continues to get inundated with memory safety bugs that no amount of infrastructure, testing, code review, etc is catching. Linux is written by monkeys with a few Hamiltons doing their best to review everything before merging.

    Linus has talked about this repeatedly over the past few years at numerous conferences and there’s a reason he’s integrating Rust drivers and subsystems (and not asking them to fork as you are suggesting) to stop the kernel stagnating and to begin to address the issues like one-off patches that aren’t maintained by their original author and to start squashing the volume of memory corruption bugs that are causing 2/3rds of the kernel’s vulnerabilities.

    • @[email protected]
      -21•4 months ago

      the kernel continues to get inundated with memory safety bugs that no amount of infrastructure, testing, code review, etc is catching.

      I’d say this is the issue to fix. It’s not easy but if anything curl has proven it can be done efficiently.

      • troed
        33•4 months ago

        Yeah, let’s see what Bagder has to say about this:

        C is unsafe and always will be

        The C programming language is not memory-safe. Among the 150 reported curl CVEs, we have determined that 61 of them are “C mistakes”. Problems that most likely would not have happened had we used a memory-safe language. 40.6% of the vulnerabilities in curl reported so far could have been avoided by using another language.

        Rust is virtually the only memory-safe language that is starting to become viable.

        https://daniel.haxx.se/blog/2023/12/13/making-it-harder-to-do-wrong/

        • @MotoAsh
          4•4 months ago

          Memory safe language that’s becoming viable … as a proper replacement of C.

          There are many other memory safe languages out there. Just not ones most would like to pull in to the kernel…

          • @qqq
            6•4 months ago

            The vast majority wouldn’t be able to be pulled into the kernel since they rely on the existence of the kernel via syscalls.