linux-kernel - [perf tool] record failure with 3.14-rc4

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

Message-ID: <20140224172440.GF2553@mudshark.cambridge.arm.com>
Date:	Mon, 24 Feb 2014 17:24:41 +0000
From:	Will Deacon <will.deacon@....com>
To:	adrian.hunter@...el.com, jolsa@...hat.com, acme@...hat.com,
	a.p.zijlstra@...llo.nl
Cc:	linux-kernel@...r.kernel.org
Subject: [perf tool] record failure with 3.14-rc4

Hi guys,

If I try to run perf record as a non-root user, I end up with the following
(unhelpful) error:

  $ perf record -e cycles ls
  [...]
  Not enough memory for reading perf file header

This is because the addresses in /proc/kallsyms always read as 0x0 when
viewed by a non-privileged user, causing kallsyms__get_function_start to
return 0x0 in args.start. machine__create_kernel_maps then treats this as
an error an returns -1 to perf_session__create_kernel_maps, causing
perf_session__new to fail and perf to exit.

The perf tool code in 3.13 is perfectly happy creating maps at 0x0, but I
can see this has changed quite substantially in the recent merge window.

Any ideas? We could fix kallsyms__get_function_start to return < 0 on
failure then fix the checks in the callers. Adrian?

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