Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 2/3] perf dso: Separate libbfd and cmd addr2line caches to fix confusion
Date: Wed, 16 Sep 2026 23:54:47 +0000	[thread overview]
Message-ID: <20260916235447.703351F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916234402.437113-3-irogers@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] perf: redundant duplicate include of dso.h
--

commit 44eae5fccba5e70d2ae1177b6b716c83f9242611
Author: Ian Rogers <irogers@google.com>

perf dso: Separate libbfd and cmd addr2line caches to fix confusion

This commit separates the libbfd and command-line addr2line caches in the
dso struct to prevent type confusion during fallback. By splitting the
caches, it avoids casting a2l_data into child_process, which previously
caused arbitrary instruction address coercion and silent aborts.

> diff --git a/tools/perf/util/dso.c b/tools/perf/util/dso.c
> index df39e6ca88e6a..6510767177be5 100644
> --- a/tools/perf/util/dso.c
> +++ b/tools/perf/util/dso.c
> @@ -1,38 +1,45 @@
>  // SPDX-License-Identifier: GPL-2.0
> +#include "dso.h"
> +
> +#include <errno.h>
> +#include <stdlib.h>
> +
>  #include <asm/bug.h>
> +#include <fcntl.h>

[ ... ]

>  #include "compress.h"
> +#include "debug.h"
> +#include "dso.h"

[Severity: Low]
Is this second inclusion of dso.h intentional?

The patch already adds an include for "dso.h" at the very top of
tools/perf/util/dso.c, so this results in a redundant duplicate include
remaining in the alphabetical block.

> +#include "dsos.h"
>  #include "env.h"
>  #include "namespaces.h"
>  #include "path.h"

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260916234402.437113-1-irogers@google.com?part=2

  reply	other threads:[~2026-09-16 23:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 17:07 [PATCH v1 1/2] perf libdw: Fix Dwfl discovery with split files Ian Rogers
2026-09-14 17:07 ` [PATCH v1 2/2] perf dso: Separate libbfd and cmd addr2line caches to fix confusion Ian Rogers
2026-09-14 17:24   ` sashiko-bot
2026-09-14 17:30 ` [PATCH v1 1/2] perf libdw: Fix Dwfl discovery with split files sashiko-bot
2026-09-16  6:35 ` [PATCH v2 0/3] perf srcline: Fix addr2line cache and fallback bugs Ian Rogers
2026-09-16  6:35   ` [PATCH v2 1/3] perf libdw: Fix Dwfl discovery with split files Ian Rogers
2026-09-16  6:52     ` sashiko-bot
2026-09-16  6:35   ` [PATCH v2 2/3] perf dso: Separate libbfd and cmd addr2line caches to fix confusion Ian Rogers
2026-09-16  6:47     ` sashiko-bot
2026-09-16  6:35   ` [PATCH v2 3/3] perf libbfd: Report success when an address is found Ian Rogers
2026-09-16  6:47     ` sashiko-bot
2026-09-16 23:43   ` [PATCH v3 0/3] perf srcline: Fix addr2line cache and fallback bugs Ian Rogers
2026-09-16 23:44     ` [PATCH v3 1/3] perf libdw: Fix Dwfl discovery with split files Ian Rogers
2026-09-17  0:03       ` sashiko-bot
2026-09-16 23:44     ` [PATCH v3 2/3] perf dso: Separate libbfd and cmd addr2line caches to fix confusion Ian Rogers
2026-09-16 23:54       ` sashiko-bot [this message]
2026-09-16 23:44     ` [PATCH v3 3/3] perf libbfd: Report success when an address is found Ian Rogers
2026-09-16 23:54       ` sashiko-bot
2026-09-17  5:04     ` [PATCH v4 0/3] perf srcline: Fix addr2line cache and fallback bugs Ian Rogers
2026-09-17  5:04       ` [PATCH v4 1/3] perf libdw: Fix Dwfl discovery with split files Ian Rogers
2026-09-17  5:20         ` sashiko-bot
2026-09-17  5:04       ` [PATCH v4 2/3] perf dso: Separate libbfd and cmd addr2line caches to fix confusion Ian Rogers
2026-09-17  5:12         ` sashiko-bot
2026-09-17  5:04       ` [PATCH v4 3/3] perf libbfd: Report success when an address is found Ian Rogers
2026-09-17  5:16         ` sashiko-bot
2026-09-18 20:25     ` [PATCH v3 0/3] perf srcline: Fix addr2line cache and fallback bugs Arnaldo Carvalho de Melo

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=20260916235447.703351F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=irogers@google.com \
    --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