Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Wed, 3 Jan 2024 20:05:43 +0100 you wrote:
> Currently, it's not allowed to attach an fentry/fexit prog to another
> fentry/fexit. At the same time it's not uncommon to see a tracing
> program with lots of logic in use, and the attachment limitation
> prevents usage of fentry/fexit for performance analysis (e.g. with
> "bpftool prog profile" command) in this case. An example could be
> falcosecurity libs project that uses tp_btf tracing programs for
> offloading certain part of logic into tail-called programs, but the
> use-case is still generic enough -- a tracing program could be
> complicated and heavy enough to warrant its profiling, yet frustratingly
> it's not possible to do so use best tooling for that.
>
> [...]
Here is the summary with links:
- [bpf-next,v12,1/4] bpf: Relax tracing prog recursive attach rules
https://git.kernel.org/bpf/bpf-next/c/19bfcdf9498a
- [bpf-next,v12,2/4] selftests/bpf: Add test for recursive attachment of tracing progs
https://git.kernel.org/bpf/bpf-next/c/5c5371e069e1
- [bpf-next,v12,3/4] bpf: Fix re-attachment branch in bpf_tracing_prog_attach
https://git.kernel.org/bpf/bpf-next/c/715d82ba636c
- [bpf-next,v12,4/4] selftests/bpf: Test re-attachment fix for bpf_tracing_prog_attach
https://git.kernel.org/bpf/bpf-next/c/e02feb3f1f47
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
