linux-kernel - Re: [BUG] perf script segfault

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: <20150331142557.GB31798@krava.brq.redhat.com>
Date:	Tue, 31 Mar 2015 16:25:57 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	David Ahern <dsahern@...il.com>,
	Stephane Eranian <eranian@...gle.com>,
	Jiri Olsa <jolsa@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] perf script segfault

On Tue, Mar 31, 2015 at 11:13:26AM -0300, Arnaldo Carvalho de Melo wrote:

SNIP

> And setting tool->ordered_events to false;
> 
> What fails is perf_evlist__sample_id_all(session->evlist), I went as far as
> looking at the perf_evlist__sample_id_all call that will find a first evsel,
> with all its fields zeroed, i.e. at some point it finds out it is a pipe (perf
> script < perf.data) and seems to not read the perf_event_attr attributes, etc,
> but I need to dig deeper here to figure out this and why is it that in that
> case we end with two 'perf script' processes when I think it should be just one, etc.
> 
> So, to keep the assumptions in place I'll keep my patch, the one that David
> tested, and redo yours on top, looking as well at ways to use what is in
> perf_session, should provide a patch soon.

I was just replying to the poluted ordered_events .. I haven't tracked
the segfault totaly.. we can change that after your fix of course ;-)

jirka
--
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/