lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 06 Jul 2022 04:30:13 +0000
To:     Chuang Wang <>
Subject: Re: [PATCH v4 0/3] cleanup the legacy probe_event on failed scenario


This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <>:

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()
  - [v4,2/3] libbpf: fix wrong variable used in perf_event_uprobe_open_legacy()
  - [v4,3/3] libbpf: cleanup the legacy uprobe_event on failed add/attach_event()

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists