linux-kernel - Re: [PATCH 3/5] perf trace: Add mmap2 handler

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 23 Sep 2013 18:22:37 -0600
From:	David Ahern <dsahern@...il.com>
To:	acme@...stprotocols.net
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] perf trace: Add mmap2 handler

Arnaldo:

I see this is you perf core tree; the problem exists in Linus' tree so 
it is needed in your urgent tree as well.

David

On 9/22/13 7:44 PM, David Ahern wrote:
> 5c5e854b changed perf_event__synthesize_mmap_events to generate MMAP2
> events. Since perf-trace does not have a handler for it it dies with a
> segfault when trying to process files:
>
> perf trace -i /tmp/perf.data
> Segmentation fault
>
> Signed-off-by: David Ahern <dsahern@...il.com>
> ---
>   tools/perf/builtin-trace.c |    1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index 9c7f017..f61c968 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -1383,6 +1383,7 @@ static int trace__replay(struct trace *trace)
>
>   	trace->tool.sample	  = trace__process_sample;
>   	trace->tool.mmap	  = perf_event__process_mmap;
> +	trace->tool.mmap2	  = perf_event__process_mmap2;
>   	trace->tool.comm	  = perf_event__process_comm;
>   	trace->tool.exit	  = perf_event__process_exit;
>   	trace->tool.fork	  = perf_event__process_fork;
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/