summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2016-12-08 18:48:26 +0100
committerSteven Rostedt <rostedt@goodmis.org>2016-12-09 15:17:10 +0100
commit847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67 (patch)
treebaacd7e2a817b5c9b487251fbe2586ceef6e23a7 /kernel
parenttracing: Allow benchmark to be enabled at early_initcall() (diff)
downloadlinux-847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67.tar.xz
linux-847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67.zip
ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it
With new binutils, gcc may get smart with its optimization and change a jmp from a 5 byte jump to a 2 byte one even though it was jumping to a global function. But that global function existed within a 2 byte radius, and gcc was able to optimize it. Unfortunately, that jump was also being modified when function graph tracing begins. Since ftrace expected that jump to be 5 bytes, but it was only two, it overwrote code after the jump, causing a crash. This was fixed for x86_64 with commit 8329e818f149, with the same subject as this commit, but nothing was done for x86_32. Cc: stable@vger.kernel.org Fixes: d61f82d06672 ("ftrace: use dynamic patching for updating mcount calls") Reported-by: Colin Ian King <colin.king@canonical.com> Tested-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions