From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jackie Liu <jackieliu2113@gmail.com>
Cc: jolsa@redhat.com, linux-kernel@vger.kernel.org,
Jackie Liu <liuyun01@kylinos.cn>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v4] perf tools: perf_event_paranoid and kptr_restrict may crash on 'perf top'
Date: Tue, 16 Mar 2021 10:15:54 -0300 [thread overview]
Message-ID: <YFCvimCNsJ4NeRA1@kernel.org> (raw)
In-Reply-To: <20210316012453.1156-1-liuyun01@kylinos.cn>
Em Tue, Mar 16, 2021 at 09:24:53AM +0800, Jackie Liu escreveu:
> After install the libelf-dev package and compiling perf, kptr_restrict=2
> and perf_event_paranoid=3 will cause perf top to crash, because the
> value of /proc/kallsyms cannot be obtained, which leads to
> info->jited_ksyms == NULL. In order to solve this problem, Add a
> judgment before use.
>
> v3->v4:
> Fix memory leaks in more places
>
> v2->v3:
> free info_linear memory and move code above, don't do those extra btf
> checks.
Applied, edited the commit message to:
----
perf top: Fix BPF support related crash with perf_event_paranoid=3 + kptr_restrict
After installing the libelf-dev package and compiling perf, if we have
kptr_restrict=2 and perf_event_paranoid=3 'perf top' will crash because
the value of /proc/kallsyms cannot be obtained, which leads to
info->jited_ksyms == NULL. In order to solve this problem, Add a
check before use.
Also plug some leaks on the error path.
----
> Suggested-by: Jiri Olsa <jolsa@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
> ---
> tools/perf/util/bpf-event.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/bpf-event.c b/tools/perf/util/bpf-event.c
> index 57d58c81a5f8..cdecda1ddd36 100644
> --- a/tools/perf/util/bpf-event.c
> +++ b/tools/perf/util/bpf-event.c
> @@ -196,25 +196,32 @@ static int perf_event__synthesize_one_bpf_prog(struct perf_session *session,
> }
>
> if (info_linear->info_len < offsetof(struct bpf_prog_info, prog_tags)) {
> + free(info_linear);
> pr_debug("%s: the kernel is too old, aborting\n", __func__);
> return -2;
> }
>
> info = &info_linear->info;
> + if (!info->jited_ksyms) {
> + free(info_linear);
> + return -1;
> + }
>
> /* number of ksyms, func_lengths, and tags should match */
> sub_prog_cnt = info->nr_jited_ksyms;
> if (sub_prog_cnt != info->nr_prog_tags ||
> - sub_prog_cnt != info->nr_jited_func_lens)
> + sub_prog_cnt != info->nr_jited_func_lens) {
> + free(info_linear);
> return -1;
> + }
>
> /* check BTF func info support */
> if (info->btf_id && info->nr_func_info && info->func_info_rec_size) {
> /* btf func info number should be same as sub_prog_cnt */
> if (sub_prog_cnt != info->nr_func_info) {
> pr_debug("%s: mismatch in BPF sub program count and BTF function info count, aborting\n", __func__);
> - err = -1;
> - goto out;
> + free(info_linear);
> + return -1;
> }
> if (btf__get_from_id(info->btf_id, &btf)) {
> pr_debug("%s: failed to get BTF of id %u, aborting\n", __func__, info->btf_id);
> --
> 2.25.1
>
--
- Arnaldo
prev parent reply other threads:[~2021-03-16 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 1:24 [PATCH v4] perf tools: perf_event_paranoid and kptr_restrict may crash on 'perf top' Jackie Liu
2021-03-16 13:00 ` Jiri Olsa
2021-03-16 13:15 ` Arnaldo Carvalho de Melo [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=YFCvimCNsJ4NeRA1@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jackieliu2113@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyun01@kylinos.cn \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox