Re:“Rust is safe” is not some kind of absolute guarantee of ...
by yencabulator on Monday October 03, 2022 @10:02AM
(#33067643)
Yes, both need to remain options. Rust-in-kernel needs to be able to support both. That's like half of Linus's ranting there.
The other half is that kernel has a lot of rules of what is safe to be done where, and Rust has to be able to follow those rules, or not be used in those contexts. This is the GFP_ATOMIC part.
As I've said over and over, both approaches - "limp along" and "reboot before causing harm" - need to remain options, for different scenarios. Anyone who treats the one use case they're familiar with as the only one which should drive policy for everyone is doing the community a disservice.