diff options
| author | Andrii Nakryiko <andrii@kernel.org> | 2022-07-06 06:20:42 +0200 |
|---|---|---|
| committer | Andrii Nakryiko <andrii@kernel.org> | 2022-07-06 06:23:07 +0200 |
| commit | e4adceef5b0e75f000754254047af59c65295ac4 (patch) | |
| tree | 777cb0284845c78e21a0d861a5b1eab6e54f73c2 /fs/hugetlbfs/Makefile | |
| parent | Merge branch 'Introduce type match support' (diff) | |
| parent | libbpf: Cleanup the legacy uprobe_event on failed add/attach_event() (diff) | |
| download | linux-e4adceef5b0e75f000754254047af59c65295ac4.tar.xz linux-e4adceef5b0e75f000754254047af59c65295ac4.zip | |
Merge branch 'cleanup the legacy probe_event on failed scenario'
Chuang Wang says:
====================
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.
With these patches, whenever an error is returned, it ensures that
the created kprobe_event/uprobe_event is cleaned.
V1 -> v3:
- add detail commits
- call remove_kprobe_event_legacy() on failed bpf_program__attach_perf_event_opts()
v3 -> v4:
- cleanup the legacy kprobe_event on failed add/attach_event
====================
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'fs/hugetlbfs/Makefile')
0 files changed, 0 insertions, 0 deletions