# Rust for Linux developers debate kernel panic guidelines at Kangrejos 2026

> **Key takeaway:** A code review discussion at Kangrejos 2026 surfaced unresolved questions about when Rust kernel code should panic versus return errors, with implications for kernel reliability and Rust adoption in Linux.

**Published:** 2026-10-27T13:56:24+00:00 
**Source:** Linux Weekly News (LWN.net) 
**Category:** kernel-os 
**Canonical URL:** https://fosswire.org/news/rust-for-linux-developers-debate-kernel-panic-guidelines-at-.html 

## Summary
At the Kangrejos 2026 conference, kernel developer Alexandre Courbot led a discussion on establishing standards for panic behavior in Rust kernel code. Courbot, who spends much of his time on kernel code reviews, presented a collection of difficult cases he had encountered to gather opinions from the Rust for Linux developer community. The talk was explicitly framed as opinion-seeking rather than presenting finished work, reflecting the early stage of consensus-building around Rust error handling patterns in kernel contexts.

The session addressed fundamental tensions between Rust's idiomatic error handling, which often uses panic for unrecoverable errors, and kernel programming conventions where panics halt the entire system. Unlike user-space Rust, kernel Rust must weigh whether to propagate errors through return codes or trigger a full system panic, with consequences for system stability and debuggability.

## Kernel panic policy for Rust code
- **Panic vs. error propagation:** Courbot raised questions about criteria for choosing between panicking and returning `Result` errors in kernel Rust code, with panics being system-fatal unlike in user-space Rust.
- **Code review experience:** The discussion was grounded in real cases Courbot encountered during routine kernel code reviews, not theoretical concerns, indicating active friction in current Rust for Linux submissions.
- **Community consensus-building:** The talk format was explicitly designed to solicit opinions from assembled Rust for Linux developers rather than present established guidelines, showing the topic remains unresolved.
- **Error handling generality:** The scope extended beyond panics to broader error handling patterns in kernel Rust, suggesting the need for documented conventions as Rust kernel adoption grows.

## Why it matters
Clear panic guidelines will become essential as more kernel subsystems adopt Rust, affecting driver reliability and debugging workflows for distribution maintainers and hardware vendors. The outcome of this discussion will influence code review standards and may shape whether Rust is perceived as production-ready for critical kernel paths.