Next steps for Rust in the kernel

Posted Sep 21, 2022 13:30 UTC (Wed) by khim (subscriber, #9252)
In reply to: Next steps for Rust in the kernel by pbonzini
Parent article: Next steps for Rust in the kernel

> Both would have to be per-file opt-ins, of course.

Except it's not really possible. Think something like std::align: if such low-level functions are not properly marked that all these “escape analysis” quickly turns into farce.

In theory it should be possible to keep “new, clean code” and “old, dirty, code” clearly separated and then slowly rewrite things, but if you consider how long it takes to, e.g., remove strlcpy… it doesn't look feasible at all.