diff options
| author | Alexander Potapenko <[email protected]> | 2017-08-16 21:08:08 +0200 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2017-08-17 09:53:00 +0200 |
| commit | 187e91fe5e915f4b7f39b824aa422493463e443d (patch) | |
| tree | 4b2c8fe90f4d4be61b2a25ceb1c5a6fe20d6aad0 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace | |
| parent | 01578e36163cdd0e4fd61d9976de15f13364e26d (diff) | |
x86/boot/64/clang: Use fixup_pointer() to access 'next_early_pgt'
__startup_64() is normally using fixup_pointer() to access globals in a
position-independent fashion. However 'next_early_pgt' was accessed
directly, which wasn't guaranteed to work.
Luckily GCC was generating a R_X86_64_PC32 PC-relative relocation for
'next_early_pgt', but Clang emitted a R_X86_64_32S, which led to
accessing invalid memory and rebooting the kernel.
Signed-off-by: Alexander Potapenko <[email protected]>
Acked-by: Kirill A. Shutemov <[email protected]>
Cc: Dmitry Vyukov <[email protected]>
Cc: Kirill A. Shutemov <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Michael Davidson <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Fixes: c88d71508e36 ("x86/boot/64: Rewrite startup_64() in C")
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
0 files changed, 0 insertions, 0 deletions