From: Adrian Hunter <adrian.hunter@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH V2 1/9] perf tools: Fix symbol annotation for relocated kernel
Date: Thu, 30 Jan 2014 11:21:12 +0200 [thread overview]
Message-ID: <52EA1988.9050100@intel.com> (raw)
In-Reply-To: <20140130085940.GA2643@gmail.com>
On 30/01/14 10:59, Ingo Molnar wrote:
>
> * Adrian Hunter <adrian.hunter@intel.com> wrote:
>
>> On 29/01/14 20:57, Arnaldo Carvalho de Melo wrote:
>>> Em Wed, Jan 29, 2014 at 04:14:36PM +0200, Adrian Hunter escreveu:
>>>> Kernel maps map memory addresses to file offsets.
>>>> For symbol annotation, objdump needs the object VMA
>>>> addresses. For an unrelocated kernel, that is the
>>>> same as the memory address.
>>>>
>>>> The addresses passed to objdump for symbol annotation
>>>> did not take into account kernel relocation. This
>>>> patch fixes that.
>>>
>>> Question: To fix the problem reported by Linus, i.e. the very minimal
>>> fix, we only need this patch, right?
>>
>> Yes but the other fixes are needed too.
>
> So, for the specific case of kernel address layout randomization, how
> does this fix Linus's bug with KASLR enabled? How does the code
> recover the random, runtime offset of the relocated kernel, which
> varies from boot to boot?
By comparing the address of a symbol ("_text" or "_stext")
in /proc/kallsyms (or perf.data - see below) with the same
symbol in vmlinux.
perf tools call this the ref_reloc_sym and stores it in
perf.data hidden in the synthesized kernel mmap record.
e.g.
0xd8 [0x50]: event: 1
.
. ... raw event: size 80 bytes
. 0000: 01 00 00 00 01 00 50 00 ff ff ff ff 00 00 00 00 ......P.........
. 0010: 00 00 00 17 00 00 00 00 ff ff ff a8 ff ff ff ff ................
. 0020: c8 01 00 98 ff ff ff ff 5b 6b 65 72 6e 65 6c 2e ........[kernel.
. 0030: 6b 61 6c 6c 73 79 6d 73 5d 5f 73 74 65 78 74 00 kallsyms]_stext.
. 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
.
0 0xd8 [0x50]: PERF_RECORD_MMAP -1/0: [0x17000000(0xffffffffa8ffffff) @ 0xffffffff980001c8]: x [kernel.kallsyms]_stext
That tells perf tools that _stext was 0xffffffff980001c8.
Compare to vmlinux:
$ objdump -t vmlinux | grep _stext
ffffffff810001c8 g .text 0000000000000000 _stext
So the relocation is 0xffffffff980001c8 - 0xffffffff810001c8
= 0x17000000
next prev parent reply other threads:[~2014-01-30 9:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:14 [PATCH V2 0/9] perf tools: kaslr fixes Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 1/9] perf tools: Fix symbol annotation for relocated kernel Adrian Hunter
2014-01-29 18:57 ` Arnaldo Carvalho de Melo
2014-01-30 7:20 ` Adrian Hunter
2014-01-30 8:59 ` Ingo Molnar
2014-01-30 9:21 ` Adrian Hunter [this message]
2014-01-30 9:20 ` Ingo Molnar
2014-01-30 18:08 ` Arnaldo Carvalho de Melo
2014-01-30 18:12 ` Arnaldo Carvalho de Melo
2014-01-30 18:15 ` Arnaldo Carvalho de Melo
2014-01-30 20:10 ` Arnaldo Carvalho de Melo
2014-02-02 8:55 ` [tip:perf/urgent] perf symbols: " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 2/9] perf tools: Add kallsyms__get_function_start() Adrian Hunter
2014-02-02 8:55 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 3/9] perf tools: Add machine__get_kallsyms_filename() Adrian Hunter
2014-02-02 8:55 ` [tip:perf/urgent] perf machine: " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 4/9] perf tools: Set up ref_reloc_sym in machine__create_kernel_maps() Adrian Hunter
2014-02-02 8:55 ` [tip:perf/urgent] perf machine: " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 5/9] perf record: Get ref_reloc_sym from kernel map Adrian Hunter
2014-02-02 8:55 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 6/9] perf tools: Prevent the use of kcore if the kernel has moved Adrian Hunter
2014-02-02 8:56 ` [tip:perf/urgent] perf symbols: " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 7/9] perf tools: Test does not need to set up ref_reloc_sym Adrian Hunter
2014-02-02 8:56 ` [tip:perf/urgent] perf tests: No " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 8/9] perf tools: Adjust kallsyms for relocated kernel Adrian Hunter
2014-01-29 19:08 ` Arnaldo Carvalho de Melo
2014-01-30 8:10 ` Adrian Hunter
2014-01-31 18:21 ` Arnaldo Carvalho de Melo
2014-02-02 8:56 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2014-01-29 14:14 ` [PATCH V2 9/9] perf buildid-cache: Check relocation when checking for existing kcore Adrian Hunter
2014-01-29 19:14 ` Arnaldo Carvalho de Melo
2014-01-30 9:34 ` Adrian Hunter
2014-01-30 14:18 ` Arnaldo Carvalho de Melo
2014-01-30 16:35 ` Adrian Hunter
2014-02-02 8:56 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52EA1988.9050100@intel.com \
--to=adrian.hunter@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).