linux-kernel - Re: [PATCH v2 1/2] perf inject: Add --convert-callchain option

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aWa12lGzx5ulhvIs@google.com>
Date: Tue, 13 Jan 2026 13:15:06 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Ian Rogers <irogers@...gle.com>, James Clark <james.clark@...aro.org>,
	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 1/2] perf inject: Add --convert-callchain option

Hi Arnaldo,

On Tue, Jan 13, 2026 at 04:38:31PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Jan 09, 2026 at 05:17:14PM -0800, Namhyung Kim wrote:
> > There are applications not built with frame pointers, so DWARF is needed
> > to get the stack traces.  So `perf record --call-graph dwarf` saves the
> > stack and register data for each sample to get the stacktrace offline.
> > But sometimes those data may have sensitive information and we don't
> > want to keep them in the file.
> > 
> > This perf inject --convert-callchain option parses the callchains and
> > discard the stack and register after that.  This will save storage space
> > and processing time for the new data file.  Of course, users should
> > remove the original data file. :)
> 
> This made me think for a while to finally realize this is not a general
> purpose "convert callchain" option, but one that converts to ip-based
> callchains specificaly, useful and probably can stay with this name, or
> maybe we could use --resolve-callchains as we use
> thread__resolve_callchain() for that anyway?

IIUC resolving callchain is to get DSO/map and symbol from raw data.
But I admit the name is general but have no other idea. :)

Thanks,
Namhyung