From: Daniel Borkmann <daniel@iogearbox.net>
To: Artem Savkov <asavkov@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Daniel Vacek <dvacek@redhat.com>, Jiri Olsa <olsajiri@gmail.com>,
Song Liu <song@kernel.org>
Subject: Re: [PATCH bpf-next 0/4] destructive bpf kfuncs (was: bpf_panic)
Date: Thu, 21 Jul 2022 15:00:56 +0200 [thread overview]
Message-ID: <d6a19eb9-92ca-eeda-ff72-8f9250d754b8@iogearbox.net> (raw)
In-Reply-To: <20220720114652.3020467-1-asavkov@redhat.com>
On 7/20/22 1:46 PM, Artem Savkov 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.
>
> This patchset tries to solve this problem by allowing properly marked tracing
> bpf programs to call crash_kexec() kernel function.
>
> This is a continuation of bpf_panic patchset with initial feedback taken into
> account.
>
> Changes from RFC:
> - sysctl knob dropped
> - using crash_kexec() instead of panic()
> - using kfuncs instead of adding a new helper
>
> Artem Savkov (4):
> bpf: add BPF_F_DESTRUCTIVE flag for BPF_PROG_LOAD
> bpf: add destructive kfunc set
> selftests/bpf: add destructive kfunc tests
> bpf: export crash_kexec() as destructive kfunc
First and second patch ccould be folded together into one. The selftest
should be last in series so that if people bisect the test won't fail due
to missing functionality. First one also has a stale comment wrt bpf_panic()
helper.
> include/linux/bpf.h | 1 +
> include/linux/btf.h | 2 +
> include/uapi/linux/bpf.h | 6 +++
> kernel/bpf/syscall.c | 4 +-
> kernel/bpf/verifier.c | 12 ++++++
> kernel/kexec_core.c | 22 ++++++++++
> net/bpf/test_run.c | 12 +++++-
> tools/include/uapi/linux/bpf.h | 6 +++
> .../selftests/bpf/prog_tests/kfunc_call.c | 41 +++++++++++++++++++
> .../bpf/progs/kfunc_call_destructive.c | 14 +++++++
> 10 files changed, 118 insertions(+), 2 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/progs/kfunc_call_destructive.c
>
prev parent reply other threads:[~2022-07-21 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 11:46 [PATCH bpf-next 0/4] destructive bpf kfuncs (was: bpf_panic) Artem Savkov
2022-07-20 11:46 ` [PATCH bpf-next 1/4] bpf: add BPF_F_DESTRUCTIVE flag for BPF_PROG_LOAD Artem Savkov
2022-07-21 14:02 ` Alexei Starovoitov
2022-07-22 4:18 ` Artem Savkov
2022-07-22 4:32 ` Alexei Starovoitov
2022-07-25 9:27 ` Artem Savkov
2022-07-25 19:23 ` Daniel Xu
2022-07-20 11:46 ` [PATCH bpf-next 2/4] bpf: add destructive kfunc set Artem Savkov
2022-07-20 11:46 ` [PATCH bpf-next 3/4] selftests/bpf: add destructive kfunc tests Artem Savkov
2022-07-20 11:46 ` [PATCH bpf-next 4/4] bpf: export crash_kexec() as destructive kfunc Artem Savkov
2022-07-21 13:00 ` Daniel Borkmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6a19eb9-92ca-eeda-ff72-8f9250d754b8@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=aarcange@redhat.com \
--cc=andrii@kernel.org \
--cc=asavkov@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dvacek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=song@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox