[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165708181330.8854.12108796366589319716.git-patchwork-notify@kernel.org>
Date: Wed, 06 Jul 2022 04:30:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Chuang Wang <nashuiliang@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH v4 0/3] cleanup the legacy probe_event on failed scenario
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Wed, 29 Jun 2022 23:18:44 +0800 you wrote:
> A potential scenario, when an error is returned after
> add_uprobe_event_legacy() in perf_event_uprobe_open_legacy(), or
> bpf_program__attach_perf_event_opts() in
> bpf_program__attach_uprobe_opts() returns an error, the uprobe_event
> that was previously created is not cleaned.
>
> At the same time, the legacy kprobe_event also have similar problems.
>
> [...]
Here is the summary with links:
- [v4,1/3] libbpf: cleanup the legacy kprobe_event on failed add/attach_event()
https://git.kernel.org/bpf/bpf-next/c/8094029330a2
- [v4,2/3] libbpf: fix wrong variable used in perf_event_uprobe_open_legacy()
https://git.kernel.org/bpf/bpf-next/c/5666fc997ccb
- [v4,3/3] libbpf: cleanup the legacy uprobe_event on failed add/attach_event()
https://git.kernel.org/bpf/bpf-next/c/2655144fb49b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists