linux-kernel - Re: [PATCH] perf tool sort: Use default sort if evlist is empty

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: <20170724074729.GD8645@krava>
Date:   Mon, 24 Jul 2017 09:47:29 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Namhyung Kim <namhyung@...nel.org>
Cc:     David Carrillo-Cisneros <davidcc@...gle.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Andi Kleen <ak@...ux.intel.com>, Simon Que <sque@...omium.org>,
        Wang Nan <wangnan0@...wei.com>, Jiri Olsa <jolsa@...nel.org>,
        Stephane Eranian <eranian@...gle.com>,
        Paul Turner <pjt@...gle.com>, kernel-team@....com
Subject: Re: [PATCH] perf tool sort: Use default sort if evlist is empty

On Sun, Jul 23, 2017 at 08:09:49AM +0900, Namhyung Kim wrote:

SNIP

> > > also I've got another crash for (added -a option for above example):
> > >
> > >         [root@...va perf]# ./perf record -e 'sched:sched_switch' -a sleep 1 |  ./perf report
> > >         # To display the perf.data header info, please use --header/--header-only options.
> > >         #
> > >         [ perf record: Woken up 1 times to write data ]
> > >         [ perf record: Captured and wrote 0.000 MB (null) ]
> > >         Segmentation fault (core dumped)
> > >
> > > catchsegv got:
> > >         /home/jolsa/kernel/linux-perf/tools/perf/util/ordered-events.c:85(free_dup_event)[0x51a6a5]
> > >         ./perf(ordered_events__free+0x5c)[0x51b0b7]
> > >         /home/jolsa/kernel/linux-perf/tools/perf/util/session.c:1751(__perf_session__process_pipe_events)[0x518abb]
> > >         ./perf(perf_session__process_events+0x91)[0x5190f0]
> > >         /home/jolsa/kernel/linux-perf/tools/perf/builtin-report.c:598(__cmd_report)[0x443a91]
> > >         ./perf(cmd_report+0x169b)[0x4455a3]
> > >         /home/jolsa/kernel/linux-perf/tools/perf/perf.c:296(run_builtin)[0x4be1b0]
> > >         /home/jolsa/kernel/linux-perf/tools/perf/perf.c:348(handle_internal_command)[0x4be41d]
> > >         /home/jolsa/kernel/linux-perf/tools/perf/perf.c:395(run_argv)[0x4be56f]
> > >         ./perf(main+0x2d6)[0x4be949]
> > >         /lib64/libc.so.6(__libc_start_main+0xf1)[0x7f3de8a10401]
> > >         ./perf(_start+0x2a)[0x42831a]
> > >
> > > looks like some mem corruption.. will try to follow up
> > > on this later if nobody beats me to it ;-)
> > 
> > Cannot reproduce it in acme's perf/core building the tool with
> >   make NO_LIBPYTHON=1 LDFLAGS=-static
> > 
> > If you have a file with the perf record output causing perf report's
> > crash, I'd like to take a look.

hm, I can't reproduce any longer.. :-\

jirka