x86/efi: Enforce CONFIG_RELOCATABLE for EFI boot stub
commit465502e733e8b8f5cf09caf5427ce75d73f59276
authorMatt Fleming <matt.fleming@intel.com>
Fri, 11 Jul 2014 07:45:25 +0000 (11 08:45 +0100)
committerJiri Slaby <jslaby@suse.cz>
Wed, 3 Sep 2014 19:31:31 +0000 (3 21:31 +0200)
tree182cf1daa152d199530738faf27d481109ab4154
parentde17f3c902e67f9a5363b4d7558968f6aafeea3f
x86/efi: Enforce CONFIG_RELOCATABLE for EFI boot stub

commit 7b2a583afb4ab894f78bc0f8bd136e96b6499a7e upstream.

Without CONFIG_RELOCATABLE the early boot code will decompress the
kernel to LOAD_PHYSICAL_ADDR. While this may have been fine in the BIOS
days, that isn't going to fly with UEFI since parts of the firmware
code/data may be located at LOAD_PHYSICAL_ADDR.

Straying outside of the bounds of the regions we've explicitly requested
from the firmware will cause all sorts of trouble. Bruno reports that
his machine resets while trying to decompress the kernel image.

We already go to great pains to ensure the kernel is loaded into a
suitably aligned buffer, it's just that the address isn't necessarily
LOAD_PHYSICAL_ADDR, because we can't guarantee that address isn't in-use
by the firmware.

Explicitly enforce CONFIG_RELOCATABLE for the EFI boot stub, so that we
can load the kernel at any address with the correct alignment.

Reported-by: Bruno Prémont <bonbons@linux-vserver.org>
Tested-by: Bruno Prémont <bonbons@linux-vserver.org>
Cc: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
arch/x86/Kconfig