On Tue Jun 23, 2026 at 1:04 PM CEST, Philipp Stanner wrote: > with a hyper-strict definition (note that I'm unsure whether calling > synchronize_rcu() in atomic context is actually even defined behavior; > I think it is. I'm just brainstorming here)
>From the Rust side of things this is well defined; please see [1] and [2]. However, given the kernel context, things such as deadlocks have more consequences than in userspace. Which is why it is still desirable to catch them (e.g. with tools like klint). [1] https://doc.rust-lang.org/reference/behavior-considered-undefined.html [2] https://doc.rust-lang.org/reference/behavior-not-considered-unsafe.html
