Asahi Linux lead developer Hector Martin resigns from Linux kernel

Original Article ↗ Hacker News Discussion ↗

Immediate Trigger

  • The Asahi Linux lead announced they are stepping down as an upstream kernel maintainer and will keep Apple/ARM work downstream.
  • The resignation followed a long-running dispute around Rust support in the kernel and a sharply worded email from the kernel project lead criticizing their behavior.

Rust DMA Abstraction Dispute

  • A Rust-for-Linux contributor proposed a Rust wrapper for the DMA subsystem so Rust drivers (e.g., Apple GPU) can use DMA safely.
  • The DMA maintainer refused, arguing:
    • They do not want a multi-language core and will “do everything” to stop cross-language abstractions.
    • Rust wrappers create a downstream dependency that could increase their maintenance burden or block C changes if Rust builds break.
  • Rust developers countered:
    • The wrapper was outside the DMA maintainer’s tree and would be maintained by Rust folks.
    • They accept that C changes can break Rust and commit to fixing Rust code without blocking C.
    • Rejecting a central wrapper forces copy‑pasted DMA code in each Rust driver, which is worse for maintainability.

Social Media and Linus’s Intervention

  • The Asahi lead publicly framed the maintainer’s stance as sabotage and suggested “shaming on social media” as the only lever left.
  • Several kernel developers, including Rust contributors, said this was unhelpful “brigading” that creates collateral damage and extra work.
  • The project lead stepped in only at this point, saying:
    • The development process “works” despite imperfections.
    • Technical arguments belong on the mailing list; social-media pressure is unacceptable.
    • The Asahi lead should consider that they might be the problem.

Governance, Culture, and Process

  • Some posters see a systemic problem: individual maintainers can effectively veto key Rust integration, while top leadership stays hands‑off until drama spills onto social media.
  • Others argue maintainers are entitled to refuse work they can’t or won’t support, and anyone unhappy is free to fork the kernel.
  • There is concern about aging maintainers, hostility deterring new contributors, and whether the kernel can sustain itself long‑term under current norms.
  • The email‑patch workflow and mailing‑list culture are widely described as hard to approach, slow, and opaque; defenders say it’s decentralized, scalable, and optimized for existing maintainers.

Rust vs C and Multi-language Codebases

  • One side: a multi-language kernel is inherently harder to maintain; everyone knows C, and Rust expertise and tooling are more fragile.
  • The other side: Rust demonstrably reduces memory‑safety bugs; treating it as “cancer” in the codebase is dismissive and political rather than technical.
  • Some suggest that if Rust can’t be fairly evaluated upstream, its supporters should invest in independent Rust-based kernels or long‑lived downstream forks instead.