linux-kernel - [BUG] perf report: bogus event group name reported

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>] [day] [month] [year] [list]

Message-ID: <CABPqkBRq7-ubdjk_3jXHXYDHOH_zSg+Grob7QnzLk3f43+9wUQ@mail.gmail.com>
Date:	Fri, 15 Nov 2013 12:41:00 +0100
From:	Stephane Eranian <eranian@...gle.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Namhyung Kim <namhyung.kim@....com>, Jiri Olsa <jolsa@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"mingo@...e.hu" <mingo@...e.hu>, David Ahern <dsahern@...il.com>,
	Vince Weaver <vincent.weaver@...ne.edu>
Subject: [BUG] perf report: bogus event group name reported

Hi,

Testing event group in sampling mode and finding
issues on the reporting side:

$ perf record --group -e 'grp1{cycles,instructions}' noploop 1
$ perf report --group  --stdio
...
# group: M^B{cycles,instructions}
             ^^^^ broken group name

# ========
#
# Samples: 8K of event '[binfmt_misc] { cycles, instructions }'
                                   ^^^^^^^^^^^^^^ broken event group name

# Event count (approx.): 7024115127
#
#         Overhead  Command      Shared Object                       Symbol
# ................  .......  .................  ...........................
#
    99.96%  99.97%  noploop  noploop            [.] main
     0.03%   0.03%  noploop  [kernel.kallsyms]  [k] apic_timer_interrupt
     0.01%   0.01%  noploop  [kernel.kallsyms]  [k] find_get_page
--
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/