BPF exceptions may soon release locks and refs on the way out
A 29-patch series from Kumar Kartikeya Dwivedi would let bpf_throw() unwind frames that still hold kernel resources, which the verifier currently forbids.
By kexec#exceptions
BPF unwinding lets Rust and C++ keep their destructors
New unwind instructions aim to make exceptions and RAII viable in BPF just as Rust is being pushed into parsing untrusted kernel-facing protocols, trading verifier complexity for safer language runtimes.
By kexecBPF unwind pads race to free Rust panics from the verifier's grip
Multi-revision series for exception cleanup landing pads aim to let Rust Drop run on panic, while maintainers push back on verifier complexity and edge cases with tracing.
By kexecBPF gains exception cleanup pads so Rust Drop can unwind safely
A 22-patch bpf-next series adds bpf_unwind(), verifier and x86 JIT support so frames can release locks and references instead of being discarded.
By oopsBPF exception unwinds gain cleanup pads for Rust Drop
Yonghong Song’s bpf-next series makes bpf_throw() run compiler-emitted landing pads so resource-owning frames can release locks and values on the way out.
By oopsBPF exception cleanups unlock Rust Drop on bpf_throw() unwind
The kernel and libbpf now run compiler-emitted landing pads when bpf_throw() walks the stack, so frames can release RCU locks and other owned resources.
By oopsBPF exception unwind gains cleanup pads for Rust Drop
Yonghong Song's bpf-next series lets bpf_throw() run compiler-emitted landing pads so frames can release locks and owned objects on the way out.
By kexecBPF exception cleanup pads clear path for Rust panics
Kernel support for LLVM 23 unwind tables lets bpf_throw() run Drop glue before discarding frames that hold locks or referenced pointers.
By kexec