linux-kernel - Re: [PATCH v2] perf record: Make sure to update build-ID cache

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176253794340.371147.16125840852097744838.b4-ty@kernel.org>
Date: Fri, 07 Nov 2025 09:52:23 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>, 
 Ian Rogers <irogers@...gle.com>, James Clark <james.clark@...aro.org>, 
 Namhyung Kim <namhyung@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>, 
 Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>, 
 LKML <linux-kernel@...r.kernel.org>, linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v2] perf record: Make sure to update build-ID cache

On Thu, 06 Nov 2025 11:00:23 -0800, Namhyung Kim wrote:
> Recent change on enabling --buildid-mmap by default brought an issue
> with build-id handling.  With build-ID in MMAP2 records, we don't need
> to save the build-ID table in the header of a perf data file.
> 
> But the actual file contents still need to be cached in the debug
> directory for annotation etc.  Split the build-ID header processing and
> caching and make sure perf record to save hit DSOs in the build-ID cache
> by moving perf_session__cache_build_ids() to the end of the record__
> finish_output().
> 
> [...]
Applied to perf-tools-next, thanks!

Best regards,
Namhyung