From: Namhyung Kim <namhyung@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 04/10] perf symbol: Set binary/symtab type for split kallsyms
Date: Fri, 9 Oct 2026 22:42:25 -0700 [thread overview]
Message-ID: <asnQQdxAoS2SqvC6@z2> (raw)
In-Reply-To: <sashiko-outbox-162542@kernel.org>
On Tue, Oct 06, 2026 at 11:58:36PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] perf: Incorrect binary_type copied to split kallsyms DSOs
> --
>
> commit caef899ba7808ad89c1adfe535b155dac7c2ebd1
> Author: Namhyung Kim <namhyung@kernel.org>
>
> perf symbol: Set binary/symtab type for split kallsyms
>
> When it creates new DSOs for split kallsyms, set the binary and symtab
> type to KALLSYMS properly.
>
> > diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> > index cf099cbd29f26..fc6e4dff282bc 100644
> > --- a/tools/perf/util/symbol.c
> > +++ b/tools/perf/util/symbol.c
> > @@ -1099,6 +1099,8 @@ static int maps__split_kallsyms(struct maps *kmaps, struct dso *dso, u64 delta,
> > return -1;
> >
> > dso__set_kernel(ndso, dso__kernel(dso));
> > + dso__set_binary_type(ndso, dso__binary_type(dso));
> > + dso__set_symtab_type(ndso, dso__symtab_type(dso));
>
> [Severity: Medium]
> Are we copying an outdated binary_type into the new split DSOs here?
>
> Looking at the execution flow, maps__split_kallsyms() is called via
> dso__load_kallsyms() from within dso__load_kernel_sym():
>
> dso__load_kernel_sym() {
> ...
> do_kallsyms:
> err = dso__load_kallsyms(dso, kallsyms_filename, map);
> ...
> if (err > 0 && !dso__is_kcore(dso)) {
> ...
> dso__set_binary_type(dso, DSO_BINARY_TYPE__KALLSYMS);
> ...
> }
>
> Because dso__load_kallsyms() executes before dso__load_kernel_sym() updates
> the parent dso's binary_type to DSO_BINARY_TYPE__KALLSYMS, the value returned
> by dso__binary_type(dso) during the split operation may still be the old
> stale value.
>
> Could this prevent the split kallsyms DSOs from receiving the correct
> binary and symtab types?
Good point, I'll just set it to DSO_BINARY_TYPE__KALLSYMS then.
Thanks,
Namhyung
>
> > dso__set_loaded(ndso);
> >
> > curr_map = map__new2(pos->start, ndso);
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20261006234315.920817-1-namhyung@kernel.org?part=4
next prev parent reply other threads:[~2026-10-10 5:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 23:43 [PATCH v2 00/10] perf symbol: Properly set DSO binary/symtab types Namhyung Kim
2026-10-06 23:43 ` [PATCH v2 01/10] perf tools: Remove redundant dso data init Namhyung Kim
2026-10-06 23:49 ` sashiko-bot
2026-10-06 23:43 ` [PATCH v2 02/10] perf tools: Try linked debug files for DSO debug info Namhyung Kim
2026-10-06 23:54 ` sashiko-bot
2026-10-10 5:38 ` Namhyung Kim
2026-10-06 23:43 ` [PATCH v2 03/10] perf symbol: Update symtab type of vmlinux from build-id cache Namhyung Kim
2026-10-06 23:54 ` sashiko-bot
2026-10-06 23:43 ` [PATCH v2 04/10] perf symbol: Set binary/symtab type for split kallsyms Namhyung Kim
2026-10-06 23:58 ` sashiko-bot
2026-10-10 5:42 ` Namhyung Kim [this message]
2026-10-06 23:43 ` [PATCH v2 05/10] perf symbol: Set dso symtab type for libbfd Namhyung Kim
2026-10-06 23:57 ` sashiko-bot
2026-10-10 5:49 ` Namhyung Kim
2026-10-06 23:43 ` [PATCH v2 06/10] perf tools: Factor out dso__find_binary_type() Namhyung Kim
2026-10-07 0:04 ` sashiko-bot
2026-10-10 6:17 ` Namhyung Kim
2026-10-06 23:43 ` [PATCH v2 07/10] perf symbol: Set binary type for JIT map DSOs Namhyung Kim
2026-10-06 23:51 ` sashiko-bot
2026-10-06 23:43 ` [PATCH v2 08/10] perf symbol: Do not set binary type from symtab type Namhyung Kim
2026-10-06 23:57 ` sashiko-bot
2026-10-10 6:41 ` Namhyung Kim
2026-10-06 23:43 ` [PATCH v2 09/10] perf annotate: Simplify symbol__disassemble() with dso binary_type Namhyung Kim
2026-10-07 0:01 ` sashiko-bot
2026-10-10 6:47 ` Namhyung Kim
2026-10-06 23:43 ` [PATCH v2 10/10] perf test: Fix dso data tests Namhyung Kim
2026-10-06 23:59 ` sashiko-bot
2026-10-10 6:48 ` Namhyung Kim
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=asnQQdxAoS2SqvC6@z2 \
--to=namhyung@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.