diff options
author | Josh Poimboeuf <jpoimboe@redhat.com> | 2016-06-15 15:45:58 -0500 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2016-07-10 17:15:58 +0200 |
commit | 0ea5ad869c85ac604f3e022bf2c5bef54838433b (patch) | |
tree | 6e1f6f929a032dfec45fab1f6c320a236899bf50 /kernel/cpu.c | |
parent | ee40fb2948fc99096836995d4f3ddcc0efbac790 (diff) | |
download | linux-stable-0ea5ad869c85ac604f3e022bf2c5bef54838433b.tar.gz linux-stable-0ea5ad869c85ac604f3e022bf2c5bef54838433b.tar.bz2 linux-stable-0ea5ad869c85ac604f3e022bf2c5bef54838433b.zip |
objtool: Fix STACK_FRAME_NON_STANDARD macro checking for function symbols
Mathieu Desnoyers reported that the STACK_FRAME_NON_STANDARD macro
wasn't working with the lttng_filter_interpret_bytecode() function in
the lttng-modules code.
Usually the relocation created by STACK_FRAME_NON_STANDARD creates a
reference to a section symbol like this:
Offset Type Value Addend Name
000000000000000000 X86_64_64 000000000000000000 +3136 .text
But in this case it created a reference to a function symbol:
Offset Type Value Addend Name
000000000000000000 X86_64_64 0x00000000000003a0 +0 lttng_filter_interpret_bytecode
To be honest I have no idea what causes gcc to decide to do one over the
other. But both are valid ELF, so add support for the function symbol.
Reported-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: lttng-dev@lists.lttng.org
Link: http://lkml.kernel.org/r/9cee42843bc6d94e990a152e4e0319cfdf6756ef.1466023450.git.jpoimboe@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'kernel/cpu.c')
0 files changed, 0 insertions, 0 deletions