From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 bpf 0/5] Fix BPF multi-uprobe PID filtering logic
Date: Sat, 25 May 2024 17:50:31 +0000 [thread overview]
Message-ID: <171665943175.11416.9298090720554703908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240521163401.3005045-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 21 May 2024 09:33:56 -0700 you wrote:
> It turns out that current implementation of multi-uprobe PID filtering logic
> is broken. It filters by thread, while the promise is filtering by process.
> Patch #1 fixes the logic trivially. The rest is testing and mitigations that
> are necessary for libbpf to not break users of USDT programs.
>
> v1->v2:
> - fix selftest in last patch (CI);
> - use semicolon in patch #3 (Jiri).
>
> [...]
Here is the summary with links:
- [v2,bpf,1/5] bpf: fix multi-uprobe PID filtering logic
https://git.kernel.org/bpf/bpf/c/46ba0e49b642
- [v2,bpf,2/5] bpf: remove unnecessary rcu_read_{lock,unlock}() in multi-uprobe attach logic
https://git.kernel.org/bpf/bpf/c/4a8f635a6054
- [v2,bpf,3/5] libbpf: detect broken PID filtering logic for multi-uprobe
https://git.kernel.org/bpf/bpf/c/04d939a2ab22
- [v2,bpf,4/5] selftests/bpf: extend multi-uprobe tests with child thread case
https://git.kernel.org/bpf/bpf/c/70342420a1cf
- [v2,bpf,5/5] selftests/bpf: extend multi-uprobe tests with USDTs
https://git.kernel.org/bpf/bpf/c/198034a87dfe
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-05-25 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 16:33 [PATCH v2 bpf 0/5] Fix BPF multi-uprobe PID filtering logic Andrii Nakryiko
2024-05-21 16:33 ` [PATCH v2 bpf 1/5] bpf: fix " Andrii Nakryiko
2024-05-21 16:33 ` [PATCH v2 bpf 2/5] bpf: remove unnecessary rcu_read_{lock,unlock}() in multi-uprobe attach logic Andrii Nakryiko
2024-05-21 16:33 ` [PATCH v2 bpf 3/5] libbpf: detect broken PID filtering logic for multi-uprobe Andrii Nakryiko
2024-05-21 16:34 ` [PATCH v2 bpf 4/5] selftests/bpf: extend multi-uprobe tests with child thread case Andrii Nakryiko
2024-05-22 7:46 ` Jiri Olsa
2024-05-21 16:34 ` [PATCH v2 bpf 5/5] selftests/bpf: extend multi-uprobe tests with USDTs Andrii Nakryiko
2024-05-25 17: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=171665943175.11416.9298090720554703908.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@meta.com \
--cc=martin.lau@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 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.