From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com, laoar.shao@gmail.com
Subject: Re: [PATCHv4 bpf-next 0/6] bpf: Add link_info support for uprobe multi link
Date: Wed, 29 Nov 2023 06:00:27 +0000 [thread overview]
Message-ID: <170123762792.21448.1297874484231140065.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231125193130.834322-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 25 Nov 2023 20:31:24 +0100 you wrote:
> hi,
> this patchset adds support to get bpf_link_info details for
> uprobe_multi links and adding support for bpftool link to
> display them.
>
> v4 changes:
> - move flags field up in bpf_uprobe_multi_link [Andrii]
> - include zero terminating byte in path_size [Andrii]
> - return d_path error directly [Yonghong]
> - use SEC(".probes") for semaphores [Yonghong]
> - fix ref_ctr_offsets leak in test [Yonghong]
> - other smaller fixes [Yonghong]
>
> [...]
Here is the summary with links:
- [PATCHv4,bpf-next,1/6] libbpf: Add st_type argument to elf_resolve_syms_offsets function
https://git.kernel.org/bpf/bpf-next/c/48f0dfd8d3e2
- [PATCHv4,bpf-next,2/6] bpf: Store ref_ctr_offsets values in bpf_uprobe array
https://git.kernel.org/bpf/bpf-next/c/4930b7f53a29
- [PATCHv4,bpf-next,3/6] bpf: Add link_info support for uprobe multi link
https://git.kernel.org/bpf/bpf-next/c/e56fdbfb06e2
- [PATCHv4,bpf-next,4/6] selftests/bpf: Use bpf_link__destroy in fill_link_info tests
https://git.kernel.org/bpf/bpf-next/c/170361288572
- [PATCHv4,bpf-next,5/6] selftests/bpf: Add link_info test for uprobe_multi link
https://git.kernel.org/bpf/bpf-next/c/147c69307bcf
- [PATCHv4,bpf-next,6/6] bpftool: Add support to display uprobe_multi links
https://git.kernel.org/bpf/bpf-next/c/a7795698f8b6
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:[~2023-11-29 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 19:31 [PATCHv4 bpf-next 0/6] bpf: Add link_info support for uprobe multi link Jiri Olsa
2023-11-25 19:31 ` [PATCHv4 bpf-next 1/6] libbpf: Add st_type argument to elf_resolve_syms_offsets function Jiri Olsa
2023-11-25 19:31 ` [PATCHv4 bpf-next 2/6] bpf: Store ref_ctr_offsets values in bpf_uprobe array Jiri Olsa
2023-11-25 19:31 ` [PATCHv4 bpf-next 3/6] bpf: Add link_info support for uprobe multi link Jiri Olsa
2023-11-27 2:17 ` Yonghong Song
2023-11-25 19:31 ` [PATCHv4 bpf-next 4/6] selftests/bpf: Use bpf_link__destroy in fill_link_info tests Jiri Olsa
2023-11-25 19:31 ` [PATCHv4 bpf-next 5/6] selftests/bpf: Add link_info test for uprobe_multi link Jiri Olsa
2023-11-27 2:19 ` Yonghong Song
2023-11-25 19:31 ` [PATCHv4 bpf-next 6/6] bpftool: Add support to display uprobe_multi links Jiri Olsa
2023-11-29 6:00 ` 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=170123762792.21448.1297874484231140065.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=laoar.shao@gmail.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox