From: Petr Mladek <pmladek@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
live-patching@vger.kernel.org
Subject: Re: [PATCH] perf symbols: ignore livepatch symbols
Date: Thu, 25 Jun 2026 11:10:36 +0200 [thread overview]
Message-ID: <ajzwjNncrI3Bob_o@pathway.suse.cz> (raw)
In-Reply-To: <20260624201254.472576-1-joe.lawrence@redhat.com>
On Wed 2026-06-24 16:12:54, Joe Lawrence wrote:
> Livepatch modules contain special symbols (prefixed by ".klp.sym.") that
> act as relocation placeholders. Once resolved, they point to the same
> addresses as the original kernel symbols they reference. [1]
>
> These special symbols confuse the 'vmlinux symtab matches kallsyms' perf
> test as kallsyms may report multiple symbols sharing a single kernel
> address. For example:
>
> kallsyms (without livepatch)
> ----------------------------
> ffffffff81a41110 T __pfx_arch_release_task_struct
> > ffffffff81a41120 T arch_release_task_struct
> ffffffff81a41140 T __pfx_exit_thread
> ffffffff81a41150 T exit_thread
>
> kallsyms (with livepatch loaded)
> ---------------------------------
> ffffffff81a41110 T __pfx_arch_release_task_struct
> > ffffffff81a41120 T arch_release_task_struct
> ffffffff81a41140 T __pfx_exit_thread
> ffffffff81a41150 T exit_thread
> > ffffffff81a41120 w .klp.sym.vmlinux.arch_release_task_struct,0 [kpatch_5_14_0_570_94_1_1_3]
>
> When perf loads kallsyms, both symbols are inserted into the
> symbol table at the same address, corrupting symbol end-address
> calculations and causing test failures.
>
> Filter out symbols prefixed with ".klp.sym." when loading kallsyms, as
> they alias existing kernel symbols.
>
> Link: https://docs.kernel.org/livepatch/module-elf-format.html#livepatch-symbols [1]
> Reported-and-tested-by: Ben Procknow <bprockno@redhat.com>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
> ---
> tools/perf/util/symbol.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> >From Ben's tests:
>
> Without patch:
> ./tools/perf/perf test 1
> 1: vmlinux symtab matches kallsyms : FAILED!
>
> With patch:
> ./tools/perf/perf test 1
> 1: vmlinux symtab matches kallsyms : Ok
>
> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> index fcaeeddbbb6b..eeaed3f5cf50 100644
> --- a/tools/perf/util/symbol.c
> +++ b/tools/perf/util/symbol.c
> @@ -774,6 +774,10 @@ static int map__process_kallsym_symbol(void *arg, const char *name,
> if (name[0] == '$')
> return 0;
It seems that the above checks has been moved into is_ignored_kernel_symbol(),
in the current Linus' tree, see
https://lore.kernel.org/lkml/20260522082604.89447-2-qirui.001@bytedance.com/
> + /* Ignore livepatch symbols */
> + if (strstarts(name, ".klp.sym."))
> + return 0;
I guess that this check should be moved there as well.
Nit: It might be possible to include <linux/livepatch_external.h>
and use KLP_SYM_PREFIX instead of ".klp.sym."
> +
> /*
> * module symbols are not sorted so we add all
> * symbols, setting length to 0, and rely on
Best Regards,
Petr
prev parent reply other threads:[~2026-06-25 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 20:12 [PATCH] perf symbols: ignore livepatch symbols Joe Lawrence
2026-06-25 9:10 ` Petr Mladek [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=ajzwjNncrI3Bob_o@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=live-patching@vger.kernel.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