[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220629151848.65587-1-nashuiliang@gmail.com>
Date: Wed, 29 Jun 2022 23:18:44 +0800
From: Chuang Wang <nashuiliang@...il.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Chuang Wang <nashuiliang@...il.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, netdev@...r.kernel.org,
bpf@...r.kernel.org
Subject: [PATCH v4 0/3] cleanup the legacy probe_event on failed scenario
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
Chuang Wang (3):
libbpf: cleanup the legacy kprobe_event on failed add/attach_event()
libbpf: fix wrong variable used in perf_event_uprobe_open_legacy()
libbpf: cleanup the legacy uprobe_event on failed add/attach_event()
tools/lib/bpf/libbpf.c | 37 +++++++++++++++++++++++++++++--------
1 file changed, 29 insertions(+), 8 deletions(-)
--
2.34.1
Powered by blists - more mailing lists