From: Namhyung Kim <namhyung@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 06/11] perf symbol: Get rid of machine_or_dso_e_machine()
Date: Tue, 13 Oct 2026 13:57:04 -0700 [thread overview]
Message-ID: <as6bIHrio0WjQnOT@google.com> (raw)
In-Reply-To: <sashiko-outbox-170240@kernel.org>
On Tue, Oct 13, 2026 at 05:37:49PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] perf symbol: NULL pointer dereference in dso__load() on error path
> --
>
> commit a7899d8622f5885c1647a9ddbd7a9ae67999aeeb
> Author: Namhyung Kim <namhyung@kernel.org>
>
> perf symbol: Get rid of machine_or_dso_e_machine()
>
> This commit removes the machine_or_dso_e_machine() fallback logic and relies
> directly on perf_env__e_machine() for kernel maps. It aims to prevent
> recursive locking issues and assumes kernel DSO architectures are correctly
> described by the machine environment.
>
> > diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> > index 56b8d75966133..a7afecb5816c2 100644
> > --- a/tools/perf/util/symbol.c
> > +++ b/tools/perf/util/symbol.c
> [ ... ]
> > @@ -1855,7 +1838,7 @@ int dso__load(struct dso *dso, struct map *map)
> > ret = dso__load_guest_kernel_sym(dso, map);
> >
> > machine = maps__machine(map__kmaps(map));
> > - if (machine && machine_or_dso_e_machine(machine, dso) == EM_X86_64)
> > + if (perf_env__e_machine(machine->env, /*e_flags=*/NULL) == EM_X86_64)
>
> [Severity: Medium]
> Does this code cause a NULL pointer dereference if machine is NULL?
>
> By removing the machine pointer guard, if map__kmaps() returns NULL (for
> example, if a kernel DSO is incorrectly associated with a non-kernel map from a
> malformed perf.data file), maps__machine() will also return NULL. Passing
> machine->env directly to perf_env__e_machine() in this state will then trigger
> a segfault.
>
> Could the machine check be restored before attempting to read its environment?
I believe machine cannot be NULL when it's from a kmap. In fact, I
think we'd better guarantee it's non-NULL for all cases. IIUC only case
it can be NULL is a test case (and it's not a kmap). I think it's better
to update the test not to pass NULL instead.
Thanks,
Namhyung
>
> > machine__map_x86_64_entry_trampolines(machine, dso);
> > goto out;
> > }
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20261013172155.160869-1-namhyung@kernel.org?part=6
next prev parent reply other threads:[~2026-10-13 20:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 17:21 [PATCH v5 00/11] perf symbol: Properly seto DSO binary/symtab types Namhyung Kim
2026-10-13 17:21 ` [PATCH v5 01/11] perf tools: Remove redundant dso data init Namhyung Kim
2026-10-13 17:25 ` sashiko-bot
2026-10-13 17:21 ` [PATCH v5 02/11] perf tools: Check ELF section type with name Namhyung Kim
2026-10-13 17:31 ` sashiko-bot
2026-10-13 20:49 ` Namhyung Kim
2026-10-13 17:21 ` [PATCH v5 03/11] perf tools: Try linked debug files for DSO debug info Namhyung Kim
2026-10-13 17:34 ` sashiko-bot
2026-10-13 20:59 ` Namhyung Kim
2026-10-13 17:21 ` [PATCH v5 04/11] perf symbol: Update symtab type of vmlinux from build-id cache Namhyung Kim
2026-10-13 17:32 ` sashiko-bot
2026-10-13 17:21 ` [PATCH v5 05/11] perf symbol: Set binary/symtab type for split kallsyms Namhyung Kim
2026-10-13 17:30 ` sashiko-bot
2026-10-13 17:21 ` [PATCH v5 06/11] perf symbol: Get rid of machine_or_dso_e_machine() Namhyung Kim
2026-10-13 17:37 ` sashiko-bot
2026-10-13 20:57 ` Namhyung Kim [this message]
2026-10-13 17:21 ` [PATCH v5 07/11] perf tools: Factor out dso__find_binary_type() Namhyung Kim
2026-10-13 17:30 ` sashiko-bot
2026-10-13 17:21 ` [PATCH v5 08/11] perf symbol: Set binary type for JIT map DSOs Namhyung Kim
2026-10-13 17:33 ` sashiko-bot
2026-10-13 17:21 ` [PATCH v5 09/11] perf symbol: Do not set binary type from symtab type Namhyung Kim
2026-10-13 17:35 ` sashiko-bot
2026-10-13 20:54 ` Namhyung Kim
2026-10-13 17:21 ` [PATCH v5 10/11] perf annotate: Simplify symbol__disassemble() with dso binary_type Namhyung Kim
2026-10-13 17:29 ` sashiko-bot
2026-10-13 17:21 ` [PATCH v5 11/11] perf test: Fix dso data tests Namhyung Kim
2026-10-13 17:30 ` sashiko-bot
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=as6bIHrio0WjQnOT@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox