Greg Kroah-Hartman, maintainer of the Linux kernel's stable branch, told attendees at Rust Week that the project urgently needs more developers capable of writing and reviewing Rust code. The appeal highlights a widening gap between the technical readiness of Rust integration and the number of engineers equipped to work with it.
Kroah-Hartman, who also maintains several kernel subsystems and has recently been applying AI tools to uncover kernel bugs, used the conference presentation to address the state of Rust in Linux directly. The infrastructure is in place. The constraint is people.
Rust now represents approximately ten percent of new code merged into the kernel, marking its shift from experimental feature to a permanent fixture. The language's compile-time memory-safety guarantees offer a practical path to reducing vulnerability classes that have long affected C-based systems code. Kernel maintainers have outlined a strategy that deploys Rust in high-risk subsystems and new drivers while keeping performance-critical and legacy code in C. The goal is risk reduction, not replacement.
Scaling the contributor base remains the unresolved challenge. Writing Rust for the kernel demands knowledge of both the language's ownership model and kernel internals. Reviewing those patches requires even deeper expertise. The project has built out documentation, integrated Rust into the build system, and stabilized toolchains, but growing the pool of qualified contributors has not kept pace. Kroah-Hartman's talk pointed toward coordinated initiatives: mentorship programs, targeted recruitment, and potentially funded engineering positions to draw experienced kernel developers into Rust work.
The urgency reflects broader industry pressure. Cloud providers, enterprise vendors, and embedded-system manufacturers are all pushing to eliminate memory-safety defects, driving demand for Rust-literate systems programmers. Kroah-Hartman's own work using AI-assisted bug detection on legacy C code illustrates a complementary approach: automate analysis of existing C while deploying Rust where it delivers the most safety benefit.
Whether the open-source community can organize fast enough remains the open question. Industry sponsorship, academic partnerships, and formal mentorship structures will likely set the pace for talent pipeline growth. For an operating system running everything from phones to supercomputers, the outcome extends well beyond kernel mailing lists.
Linux 核心穩定版維護者 Greg Kroah-Hartman 在 Rust Week 活動上向與會者表示，項目迫切需要更多能夠編寫和審查 Rust 程式碼的開發者。此呼籲突顯了 Rust 整合的技術準備就緒與具備相關能力的工程師數量之間的日益擴大差距。
Kroah-Hartman 同時維護多個核心子系統，近期亦應用 AI 工具來發掘核心錯誤。他在會議演講中直接談及 Rust 在 Linux 中的現況：基礎設施已經就位，瓶頸在於人手。
Rust 現時佔核心新合併程式碼約百分之十，標誌著它已從實驗性功能轉變為永久組成部分。該語言在編譯時提供的記憶體安全保證，為減少長期影響 C 語言系統程式碼的漏洞類別提供了切實可行的途徑。核心維護者已制定策略，在高風險子系統和新驅動程式中部署 Rust，同時將性能關鍵和舊有程式碼保留於 C。目標是降低風險，而非取代。
擴大貢獻者群體仍然是尚未解決的挑戰。為核心編寫 Rust 需要同時掌握該語言的擁有權模型和核心內部運作。審查這些 patch 則需要更深入的專業知識。項目已建立文件、將 Rust 整合至建構系統，並穩定化工具鏈，但合格貢獻者的增長速度未能跟上。Kroah-Hartman 的演講指向有組織的推動措施：導師計劃、針對性推廣，以及可能資助的工程師職位，以吸引經驗豐富的核心開發者投入 Rust 工作。
這種緊迫性反映了更廣泛的行業壓力。雲端服務供應商、企業廠商和嵌入式系統製造商均致力於消除記憶體安全缺陷，推動了對熟悉 Rust 的系統程式員的需求。Kroah-Hartman 自身利用 AI 輔助錯誤檢測於舊有 C 程式碼的工作，展示了一種互補方法：自動化分析現有 C 程式碼，同時在能帶來最大安全效益的地方部署 Rust。
開源社區能否足夠迅速地組織起來，仍然是待解之問。行業贊助、學術合作和正式的導師結構，很可能將決定人才培育渠道增長的速度。對於一個由手機至超級電腦均在運行的操作系統而言，其影響遠超核心郵件列表的範疇。