From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com, kuifeng@fb.com
Subject: Re: [PATCH bpf-next 0/3] LINK_CREATE support for fentry/tp_btf/lsm attachments
Date: Fri, 22 Apr 2022 22:40:12 +0000 [thread overview]
Message-ID: <165066721219.28625.1373870919607607891.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220421033945.3602803-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 20 Apr 2022 20:39:42 -0700 you wrote:
> Wire up ability to attach bpf_link-based fentry/fexit/fmod_ret, tp_btf
> (BTF-aware raw tracepoints), and LSM programs through universal LINK_CREATE
> command, in addition to current BPF_RAW_TRACEPOINT_OPEN.
>
> Teach libbpf to handle this LINK_CREATE/BPF_RAW_TRACEPOINT_OPEN split on older
> kernels transparently in universal low-level bpf_link_create() API for users
> convenience.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf: allow attach TRACING programs through LINK_CREATE command
https://git.kernel.org/bpf/bpf-next/c/df86ca0d2f0f
- [bpf-next,2/3] libbpf: teach bpf_link_create() to fallback to bpf_raw_tracepoint_open()
https://git.kernel.org/bpf/bpf-next/c/8462e0b46fe2
- [bpf-next,3/3] selftests/bpf: switch fexit_stress to bpf_link_create() API
https://git.kernel.org/bpf/bpf-next/c/fd0493a1e49e
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:[~2022-04-22 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 3:39 [PATCH bpf-next 0/3] LINK_CREATE support for fentry/tp_btf/lsm attachments Andrii Nakryiko
2022-04-21 3:39 ` [PATCH bpf-next 1/3] bpf: allow attach TRACING programs through LINK_CREATE command Andrii Nakryiko
2022-04-22 20:55 ` Kui-Feng Lee
2022-04-21 3:39 ` [PATCH bpf-next 2/3] libbpf: teach bpf_link_create() to fallback to bpf_raw_tracepoint_open() Andrii Nakryiko
2022-04-22 20:57 ` Kui-Feng Lee
2022-04-21 3:39 ` [PATCH bpf-next 3/3] selftests/bpf: switch fexit_stress to bpf_link_create() API Andrii Nakryiko
2022-04-22 21:02 ` Kui-Feng Lee
2022-04-22 22:40 ` 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=165066721219.28625.1373870919607607891.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=kuifeng@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.