From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/3] perf libdw: Optimize fallback logic for missing DWARF
Date: Mon, 26 Oct 2026 09:31:55 +0000 [thread overview]
Message-ID: <sashiko-outbox-184798@kernel.org> (raw)
In-Reply-To: <6cb3acf7a54ed1638ce0172a79c7e3263be17780.1792995775.git.irogers@google.com>
> When libdw encounters a DWARF definition it cannot accurately un-inline
> or an address block natively missing structural line maps,
> dwfl_module_getsrc() returns NULL. Previously, libdw__addr2line()
> returned -1 in both dwfl_module_getdwarf() and dwfl_module_getsrc()
> failure paths while addr2line() in srcline.c only stopped its fallback
> loop on ret > 0. This caused perf's addr2line_style loop to fall back to
> llvm, libbfd, and the cmd__addr2line() subprocess wrapper on every
> unmapped address or stripped DSO.
>
> Update the addr2line_style pipeline return semantics consistently:
> 1. Backends return 0 to denote conclusively missing information
> (e.g. valid ELF but no DWARF inside, or parsed DWARF with no mapped
> lines), stopping the fallback loop.
> 2. Backends (and uncompiled stubs) return < 0 to denote initialization
> or backend errors, instructing the loop to iterate to the next
> configured fallback.
> 3. Backends return > 0 on successful source line resolution.
>
> Fixes: bf96e296d52d ("perf libdw: Fix Dwfl discovery with split files")
> Signed-off-by: Ian Rogers <irogers@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1792995775.git.irogers@google.com?part=1
next prev parent reply other threads:[~2026-10-26 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 6:50 [PATCH 0/3] perf: Fix libdw addr2line fallback, pr_debugN overhead, and cumulative hist decay Ian Rogers
2026-10-26 6:50 ` [PATCH 1/3] perf libdw: Optimize fallback logic for missing DWARF Ian Rogers
2026-10-26 9:31 ` sashiko-bot [this message]
2026-10-26 6:50 ` [PATCH 2/3] perf debug: Avoid calling eprintf() in pr_debugN() when verbose < n Ian Rogers
2026-10-26 9:35 ` sashiko-bot
2026-10-26 6:50 ` [PATCH 3/3] perf hist: Do not delete cumulative caller entries before stat_acc decays Ian Rogers
2026-10-26 9:41 ` sashiko-bot
2026-10-27 20:42 ` [PATCH 0/3] perf: Fix libdw addr2line fallback, pr_debugN overhead, and cumulative hist decay 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=sashiko-outbox-184798@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