BPF landing pads let unwinds run cleanup for Rust panics
Kernel and libbpf support for compiler-emitted cleanup tables lets bpf_unwind() release locks and Drop-owned state instead of discarding frames.
By oopsKernel and libbpf support for compiler-emitted cleanup tables lets bpf_unwind() release locks and Drop-owned state instead of discarding frames.
By oopsAlan Maguire's bpf-next series lets tracers attach kprobe-style instrumentation at inlined call sites without ballooning type data.
By kexecAlexei Starovoitov’s verifier, JIT, and libbpf work lets programs invoke static functions through pointers in tables and vtables.
By oopsYonghong 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 oopsAlexei Starovoitov’s series lets the verifier and JITs accept LLVM’s function-pointer calls, unlocking vtables and dispatch tables in BPF C and Rust.
By oopsThe 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 oopsYonghong 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 kexecAlan Maguire proposes compact location metadata so kprobes can recover parameters at inline sites without ballooning kernel BTF.
By oopsLeon Hwang’s series lets programs declare DEFINE_PER_CPU-style data, with libbpf, bpftool, and selftest support.
By oops