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]
Date: Wed, 7 Feb 2024 21:29:49 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>, Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>, 
	Like Xu <like.xu.linux@...il.com>, linux-kernel@...r.kernel.org, 
	linux-perf-users@...r.kernel.org
Subject: Re: [PATCH V2 0/2] perf symbols: Slightly improve module file
 executable section mappings

On Wed, Feb 7, 2024 at 9:26 PM Namhyung Kim <namhyung@...nel.org> wrote:
>
> Hi Adrian,
>
> On Tue, Feb 6, 2024 at 5:05 AM Adrian Hunter <adrian.hunter@...elcom> wrote:
> >
> > Hi
> >
> > Currently perf does not record module section addresses except for
> > the .text section. In general that means perf cannot get module section
> > mappings correct (except for .text) when loading symbols from a kernel
> > module file. (Note using --kcore does not have this issue)
> >
> > Here are a couple of patches to help shed light upon and slightly improve
> > the situation.
> >
> >
> > Changes in V2:
> >
> >   perf tools: Make it possible to see perf's kernel and module memory mappings
> >     - add dump to perf report (if no browser) as well as perf script
> >     - add 'perf --debug kmaps' option also to dump kmaps
> >
> >
> > Adrian Hunter (2):
> >       perf tools: Make it possible to see perf's kernel and module memory mappings
> >       perf symbols: Slightly improve module file executable section mappings
>
> Acked-by: Namhyung Kim <namhyung@...nel.org>

Hmm.. this is not applied cleanly.  Can you please rebase
onto the current perf-tools-next?

Thanks,
Namhyung

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ