linux-kernel - Re: [RFC] perf report: introduce --map-anon-mem for anon-executable-memory symbols parsing

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: <20150619201021.GG31188@kernel.org>
Date:	Fri, 19 Jun 2015 17:10:21 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"Wangnan (F)" <wangnan0@...wei.com>,
	Hou Pengyang <houpengyang@...wei.com>, mingo@...hat.com,
	namhyung@...nel.org, a.p.zijlstra@...llo.nl,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] perf report: introduce --map-anon-mem for
 anon-executable-memory symbols parsing

Em Fri, Jun 19, 2015 at 12:42:14PM +0200, Ingo Molnar escreveu:
> * Wangnan (F) <wangnan0@...wei.com> wrote:
> 
> > On 2015/6/18 22:01, Hou Pengyang wrote:
> > >This patch introduces a --map-anon-mem argument to perf report to deal
> > >with anon-executable-memory symbol parsing.
> > 
> > --map-anon-mem is not a good name. The user defined map area list
> > introduced in this patch can be used on not only anon mapping but
> > also file mapping.
> 
> Yeah, so quirky options generally suck and only 0.01% of the users will use it. 
> It's in a way worse than not having this code, because we'll have to maintain it, 
> but it won't be used.
> 
> Is there a way to auto-detect 'executable anon mappings' (perhaps by generating an 
> MMAP event with some extra bit set, or a new MMAP event?) so that it's all 
> seemless?
> 
> The user should not be required to know about such details!

Also I think we shouldn't have two maps instances, i.e. if one wants to
insert some "map files", i.e. details about a map on a file, csv or any
other format (JSON anyone? :-)), or like he did, on the command line,
then it should be added to the existing per thread tree of maps, i.e.
would be useful for some super specialized corner case but wouldn't
impact the common case, i.e. no try this tree of maps, if it is not
there, then try the other, that everybody else uses, etc.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/