From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, dan.carpenter@linaro.org,
olsajiri@gmail.com, asavkov@redhat.com
Subject: Re: [PATCH bpf-next v12 0/4] Relax tracing prog recursive attach rules
Date: Fri, 05 Jan 2024 04:50:25 +0000 [thread overview]
Message-ID: <170443022570.4868.18367369657258878206.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240103190559.14750-1-9erthalion6@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
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
prev parent reply other threads:[~2024-01-05 4:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 19:05 [PATCH bpf-next v12 0/4] Relax tracing prog recursive attach rules Dmitrii Dolgov
2024-01-03 19:05 ` [PATCH bpf-next v12 1/4] bpf: " Dmitrii Dolgov
2024-01-03 19:05 ` [PATCH bpf-next v12 2/4] selftests/bpf: Add test for recursive attachment of tracing progs Dmitrii Dolgov
2024-01-03 19:47 ` Song Liu
2024-01-03 20:18 ` Dmitry Dolgov
2024-01-03 20:47 ` Song Liu
2024-01-03 20:51 ` Dmitry Dolgov
2024-01-05 4:45 ` Alexei Starovoitov
2024-01-03 19:05 ` [PATCH bpf-next v12 3/4] bpf: Fix re-attachment branch in bpf_tracing_prog_attach Dmitrii Dolgov
2024-01-03 19:05 ` [PATCH bpf-next v12 4/4] selftests/bpf: Test re-attachment fix for bpf_tracing_prog_attach Dmitrii Dolgov
2024-01-03 19:47 ` Song Liu
2024-01-05 4:50 ` patchwork-bot+netdevbpf [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=170443022570.4868.18367369657258878206.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=9erthalion6@gmail.com \
--cc=andrii@kernel.org \
--cc=asavkov@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@linux.dev \
--cc=olsajiri@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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