From: Yonghong Song <yonghong.song@linux.dev>
To: Hou Tao <houtao@huaweicloud.com>, bpf@vger.kernel.org
Cc: linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Yonghong Song <yhs@fb.com>,
Krister Johansen <kjlx@templeofstupid.com>,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next] perf/bpf: Use prog to emit ksymbol event for main program
Date: Thu, 18 Jul 2024 19:25:45 -0700 [thread overview]
Message-ID: <9e3d8130-f5a7-459d-b1f4-033c367cd838@linux.dev> (raw)
In-Reply-To: <20240714065533.1112616-1-houtao@huaweicloud.com>
On 7/13/24 11:55 PM, Hou Tao wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Since commit 0108a4e9f358 ("bpf: ensure main program has an extable"),
> prog->aux->func[0]->kallsyms is left as uninitialized. For bpf program
> with subprogs, the symbol for the main program is missed just as shown
> in the output of perf script below:
>
> ffffffff81284b69 qp_trie_lookup_elem+0xb9 ([kernel.kallsyms])
> ffffffffc0011125 bpf_prog_a4a0eb0651e6af8b_lookup_qp_trie+0x5d (bpf...)
> ffffffff8127bc2b bpf_for_each_array_elem+0x7b ([kernel.kallsyms])
> ffffffffc00110a1 +0x25 ()
> ffffffff8121a89a trace_call_bpf+0xca ([kernel.kallsyms])
>
> Fix it by always using prog instead prog->aux->func[0] to emit ksymbol
> event for the main program. After the fix, the output of perf script
> will be correct:
>
> ffffffff81284b96 qp_trie_lookup_elem+0xe6 ([kernel.kallsyms])
> ffffffffc001382d bpf_prog_a4a0eb0651e6af8b_lookup_qp_trie+0x5d (bpf...)
> ffffffff8127bc2b bpf_for_each_array_elem+0x7b ([kernel.kallsyms])
> ffffffffc0013779 bpf_prog_245c55ab25cfcf40_qp_trie_lookup+0x25 (bpf...)
> ffffffff8121a89a trace_call_bpf+0xca ([kernel.kallsyms])
>
> Fixes: 0108a4e9f358 ("bpf: ensure main program has an extable")
> Signed-off-by: Hou Tao <houtao1@huawei.com>
> ---
> Hi,
>
> ksymbol for bpf program had been broken twice, and I think it is better
> to add a bpf selftest for it, but I'm not so familiar with the
> perf_event_open(), for now I just post the fix patch and will post the
> selftest later.
>
> kernel/events/core.c | 28 +++++++++++++---------------
> 1 file changed, 13 insertions(+), 15 deletions(-)
I actually just hit this issue with patch in
https://lore.kernel.org/bpf/20240718205158.3651529-1-yonghong.song@linux.dev/T/#m92fd74865d93306757a10eb27d1e4f84cfffd5a8
This patch fixed the issue. So
Tested-by: Yonghong Song <yonghong.song@linux.dev>
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index f0128c5ff278..e1b7d9e61fa0 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -9289,21 +9289,19 @@ static void perf_event_bpf_emit_ksymbols(struct bpf_prog *prog,
> bool unregister = type == PERF_BPF_EVENT_PROG_UNLOAD;
> int i;
>
> - if (prog->aux->func_cnt == 0) {
> - perf_event_ksymbol(PERF_RECORD_KSYMBOL_TYPE_BPF,
> - (u64)(unsigned long)prog->bpf_func,
> - prog->jited_len, unregister,
> - prog->aux->ksym.name);
> - } else {
> - for (i = 0; i < prog->aux->func_cnt; i++) {
> - struct bpf_prog *subprog = prog->aux->func[i];
> -
> - perf_event_ksymbol(
> - PERF_RECORD_KSYMBOL_TYPE_BPF,
> - (u64)(unsigned long)subprog->bpf_func,
> - subprog->jited_len, unregister,
> - subprog->aux->ksym.name);
> - }
> + perf_event_ksymbol(PERF_RECORD_KSYMBOL_TYPE_BPF,
> + (u64)(unsigned long)prog->bpf_func,
> + prog->jited_len, unregister,
> + prog->aux->ksym.name);
> +
> + for (i = 1; i < prog->aux->func_cnt; i++) {
> + struct bpf_prog *subprog = prog->aux->func[i];
> +
> + perf_event_ksymbol(
> + PERF_RECORD_KSYMBOL_TYPE_BPF,
> + (u64)(unsigned long)subprog->bpf_func,
> + subprog->jited_len, unregister,
> + subprog->aux->ksym.name);
> }
> }
>
next prev parent reply other threads:[~2024-07-19 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 6:55 [PATCH bpf-next] perf/bpf: Use prog to emit ksymbol event for main program Hou Tao
2024-07-16 1:36 ` Krister Johansen
2024-07-16 7:27 ` Jiri Olsa
2024-07-19 2:25 ` Yonghong Song [this message]
2024-07-19 15:30 ` patchwork-bot+netdevbpf
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=9e3d8130-f5a7-459d-b1f4-033c367cd838@linux.dev \
--to=yonghong.song@linux.dev \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=jolsa@kernel.org \
--cc=kjlx@templeofstupid.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).