Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Wed, 10 Aug 2022 08:59:02 +0200 you wrote:
> eBPF is often used for kernel debugging, and one of the widely used and
> powerful debugging techniques is post-mortem debugging with a full memory dump.
> Triggering a panic at exactly the right moment allows the user to get such a
> dump and thus a better view at the system's state. Right now the only way to
> do this in BPF is to signal userspace to trigger kexec/panic. This is
> suboptimal as going through userspace requires context changes and adds
> significant delays taking system further away from "the right moment". On a
> single-cpu system the situation is even worse because BPF program won't even be
> able to block the thread of interest.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] bpf: add destructive kfunc flag
https://git.kernel.org/bpf/bpf-next/c/4dd48c6f1f83
- [bpf-next,v5,2/3] bpf: export crash_kexec() as destructive kfunc
https://git.kernel.org/bpf/bpf-next/c/133790596406
- [bpf-next,v5,3/3] selftests/bpf: add destructive kfunc test
https://git.kernel.org/bpf/bpf-next/c/e33894581675
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
