diff options
author | Arvind Sankar <nivedita@alum.mit.edu> | 2020-02-27 02:00:31 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2020-02-29 12:19:35 +0300 |
commit | c98a76eabbb6e7755f3d4a4c33f8fe869dda6383 (patch) | |
tree | 8d9f30d143d1b6d68863cf08d88cfc0fd2c5dff3 /tools/perf/ui | |
parent | 3e03dca500ca65b37dff0a205893095dca74f054 (diff) | |
download | linux-c98a76eabbb6e7755f3d4a4c33f8fe869dda6383.tar.xz |
x86/boot/compressed: Fix reloading of GDTR post-relocation
The following commit:
ef5a7b5eb13e ("efi/x86: Remove GDT setup from efi_main")
introduced GDT setup into the 32-bit kernel's startup_32, and reloads
the GDTR after relocating the kernel for paranoia's sake.
A followup commit:
32d009137a56 ("x86/boot: Reload GDTR after copying to the end of the buffer")
introduced a similar GDTR reload in the 64-bit kernel as well.
The GDTR is adjusted by (init_size-_end), however this may not be the
correct offset to apply if the kernel was loaded at a misaligned address
or below LOAD_PHYSICAL_ADDR, as in that case the decompression buffer
has an additional offset from the original load address.
This should never happen for a conformant bootloader, but we're being
paranoid anyway, so just store the new GDT address in there instead of
adding any offsets, which is simpler as well.
Fixes: ef5a7b5eb13e ("efi/x86: Remove GDT setup from efi_main")
Fixes: 32d009137a56 ("x86/boot: Reload GDTR after copying to the end of the buffer")
Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: x86@kernel.org
Link: https://lore.kernel.org/r/20200226230031.3011645-2-nivedita@alum.mit.edu
Diffstat (limited to 'tools/perf/ui')
0 files changed, 0 insertions, 0 deletions