From: sashiko-bot@kernel.org
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 02/15] perf debuginfo: Set DEBUGINFOD_URLS from /etc/debuginfod when unset
Date: Thu, 17 Sep 2026 16:07:54 +0000 [thread overview]
Message-ID: <20260917160754.D6ECD1F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260917155528.62607-3-acme@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] perf debuginfo: bypass of /etc/debuginfod fallback for record/buildid-cache
--
commit abf1731695e2130d2a1cbc46b0ed7ae8527966ac
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
perf debuginfo: Set DEBUGINFOD_URLS from /etc/debuginfod when unset
This commit allows perf to read DEBUGINFOD_URLS from the .urls files in
/etc/debuginfod during early setup if the environment variable is not already
configured. This aims to resolve debuginfod failures in environments like
cron jobs, systemd services, or CI pipelines where distro setup scripts
might not populate the environment.
diff --git a/tools/perf/util/util.c b/tools/perf/util/util.c
--- a/tools/perf/util/util.c
+++ b/tools/perf/util/util.c
[ ... ]
> void perf_debuginfod_setup(struct perf_debuginfod *di)
> {
[ ... ]
> - if (!di->set)
> - setenv("DEBUGINFOD_URLS", "", 1);
> - else if (di->urls && strcmp(di->urls, "system"))
> - setenv("DEBUGINFOD_URLS", di->urls, 1);
> + if (!di->set) {
> + debuginfod__set_urls_env("");
> + } else if (di->urls == NULL || !strcmp(di->urls, "system")) {
> + const char *urls = getenv(DEBUGINFOD_URLS_ENV);
> +
> + if (urls != NULL)
> + debuginfod__set_urls_env(urls);
> + } else {
> + debuginfod__set_urls_env(di->urls);
> + }
>
> - pr_debug("DEBUGINFOD_URLS=%s\n", getenv("DEBUGINFOD_URLS"));
> + debuginfod__urls_set_by_tool = true;
[Severity: Medium]
When perf tools request debuginfod support with the default "system" URLs,
and the environment variable is unset (urls == NULL), does unconditionally
setting debuginfod__urls_set_by_tool to true here unintentionally lock out
the fallback mechanism?
[ ... ]
> +#ifdef HAVE_DEBUGINFOD_SUPPORT
> +/*
> + * The debuginfod client checks its local cache only as part of the
[ ... ]
> +void debuginfod__setup_urls_env(void)
> +{
> + const char *env_urls;
> + char *urls = NULL;
> + DIR *dir;
> + struct dirent *dent;
> +
> + /*
> + * Tools that set DEBUGINFOD_URLS themselves already made their choice,
> + * leave it alone.
> + */
> + if (debuginfod__urls_set_by_tool)
> + return;
[Severity: Medium]
Because debuginfod__urls_set_by_tool is flagged to true earlier in
perf_debuginfod_setup(), will tools like perf record and perf buildid-cache
that run with --debuginfod exit early here?
It looks like this sequence causes these tools to entirely bypass the new
/etc/debuginfod fallback logic when DEBUGINFOD_URLS is unset, which seems
to defeat the purpose of the patch for these subcommands.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917155528.62607-1-acme@kernel.org?part=2
next prev parent reply other threads:[~2026-09-17 16:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 15:55 [PATCH v7 0/15] perf tools: Annotate fixes, stdio progress indication, debuginfo-client in more places Arnaldo Carvalho de Melo
2026-09-17 15:55 ` [PATCH 01/15] perf debuginfo: Fetch debuginfo keyed by build ID using debuginfod Arnaldo Carvalho de Melo
2026-09-17 16:03 ` sashiko-bot
2026-09-17 17:58 ` Ian Rogers
2026-09-17 20:36 ` Arnaldo Carvalho de Melo
2026-09-17 15:55 ` [PATCH 02/15] perf debuginfo: Set DEBUGINFOD_URLS from /etc/debuginfod when unset Arnaldo Carvalho de Melo
2026-09-17 16:07 ` sashiko-bot [this message]
2026-09-17 15:55 ` [PATCH 03/15] perf config: Move perf_config__set_variable() to util/config.c Arnaldo Carvalho de Melo
2026-09-17 16:11 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 04/15] perf debuginfo: Let the user skip and disable debuginfod fetches Arnaldo Carvalho de Melo
2026-09-17 16:05 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 05/15] perf debuginfo: Show the debuginfod fetch progress and keys in the TUI Arnaldo Carvalho de Melo
2026-09-17 16:09 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 06/15] perf symbol: Fall back to fetching the vmlinux by build ID Arnaldo Carvalho de Melo
2026-09-17 16:08 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 07/15] perf annotate-data: Show the sample count in the data-type browser Arnaldo Carvalho de Melo
2026-09-17 16:04 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 08/15] perf report: Add --progress option Arnaldo Carvalho de Melo
2026-09-17 16:02 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 09/15] perf scripts: Add perf-stuck, to tell where a running perf is stuck Arnaldo Carvalho de Melo
2026-09-17 16:04 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 10/15] perf dwarf-aux: Bound the type chases for broken debug info Arnaldo Carvalho de Melo
2026-09-17 16:03 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 11/15] perf dwarf-aux: Add die_same_file() and die_get_type_die() Arnaldo Carvalho de Melo
2026-09-17 16:09 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 12/15] perf annotate-data: Resolve type DIEs in the debug file they came from Arnaldo Carvalho de Melo
2026-09-17 16:09 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 13/15] perf annotate-data: Bound the member nesting recursion Arnaldo Carvalho de Melo
2026-09-17 16:08 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 14/15] perf mem record: Request PERF_SAMPLE_CPU by default Arnaldo Carvalho de Melo
2026-09-17 16:15 ` sashiko-bot
2026-09-17 15:55 ` [PATCH 15/15] perf mem record: Use the IBS swfilt filter when available Arnaldo Carvalho de Melo
2026-09-17 16:09 ` 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=20260917160754.D6ECD1F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acme@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.