Hector Martin (@marcan@treehouse.systems)
social.treehouse.systems
Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project: https://lwn.net/ml/all/20250131075751.GA16720@lst.de/ The good news is this doesn't affect drm/asahi, our GPU driver. The bad news is it does affect all the *other* drivers we're (re)writing in Rust, two so far with a third one coming. Another choice quote, calling R4L "cancer": https://lore.kernel.org/lkml/20250128092334.GA28548@lst.de/ Personally, I would consider this grounds for removal of Christoph from the Linux project on Code of Conduct violation grounds, but sadly I doubt much will happen other than draining a lot of people's energy and will to continue the project until Linus says "fuck you" or something. As for how to move forward, if I were one of the Rust maintainers, I would just merge the patch (which does *not* touch code formally maintained by the dissenter). Either Linus takes the pull, and whatever Christoph says is irrelevant, or he doesn't, and R4L dies. Everything else is a waste of everyone's time and energy. Edit: Sent in my 2 cents: https://lore.kernel.org/rust-for-linux/2b9b75d1-eb8e-494a-b05f-59f75c92e6ae@marcan.st/T/#m1944b6d485070970e359bbc7baa71b04c86a30af

Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project:

https://lwn.net/ml/all/20250131075751.GA16720@lst.de/

The good news is this doesn’t affect drm/asahi, our GPU driver. The bad news is it does affect all the other drivers we’re (re)writing in Rust, two so far with a third one coming.

Another choice quote, calling R4L “cancer”: https://lore.kernel.org/lkml/20250128092334.GA28548@lst.de/

Personally, I would consider this grounds for removal of Christoph from the Linux project on Code of Conduct violation grounds, but sadly I doubt much will happen other than draining a lot of people’s energy and will to continue the project until Linus says “fuck you” or something.

As for how to move forward, if I were one of the Rust maintainers, I would just merge the patch (which does not touch code formally maintained by the dissenter). Either Linus takes the pull, and whatever Christoph says is irrelevant, or he doesn’t, and R4L dies. Everything else is a waste of everyone’s time and energy.

Edit: Sent in my 2 cents: https://lore.kernel.org/rust-for-linux/2b9b75d1-eb8e-494a-b05f-59f75c92e6ae@marcan.st/T/#m1944b6d485070970e359bbc7baa71b04c86a30af

  • Lvxferre [he/him]
    64·
    9 hours ago

    Hector Martin isn’t claiming that Hellwig’s crusade is against Rust, but against R4L.

    Fair point.

    “Don’t bring new languages into the kernel” is a crusade against R4L.

    Still neither a crusade nor a personal one, unless proved contrariwise. It’s just that he’s prioritising some things and the R4L project is prioritising other things.

    • BatmanAoD@programming.dev
      7·
      7 hours ago

      I didn’t use the word “personal”, but it’s inherently somewhat personal in that it’s one person trying to fight back against a decision that Linus and GKH have both endorsed (to put Rust in the kernel). “Crusade” is strong wording, but so is “I will do anything I can to stop this.” That’s far beyond simply “prioritizing [other] things.”

      • Lvxferre [he/him]
        2·
        7 hours ago

        I’m aware that you didn’t use the word “personal”; I did. (Sorry if what I said implied otherwise, it was my bad.) My point is that Martin is making a big deal like Hellwig had some bone to pick specifically against the R4L project and Rust, you know?

        Based on the info that I currently have at hand I do think that the project will progress further, against Hellwig’s wish, and this will be a net benefit for the kernel. I just don’t see the big deal that people make of his opposition, he’s just being the old man screaming at cloud.

        • BatmanAoD@programming.dev
          2·
          7 hours ago

          But…that’s exactly what’s happening. Rust is already in the kernel, with both Linus’s and GKH’s approval. CH is trying to singlehandedly reject any use of Rust in any part of the kernel where he has maintainer status. That’s pretty specific to R4L.