Thread (23 messages) 23 messages, 8 authors, 2015-11-24
STALE3871d
Revisions (11)
  1. v3 [diff vs current]
  2. v4 [diff vs current]
  3. v4 [diff vs current]
  4. v4 [diff vs current]
  5. v4 [diff vs current]
  6. v4 [diff vs current]
  7. v4 [diff vs current]
  8. v4 current
  9. v4 [diff vs current]
  10. v4 [diff vs current]
  11. v4 [diff vs current]

[PATCH v4 3/3] arm64/efi: isolate EFI stub from the kernel proper

From: Jeremy Linton <hidden>
Date: 2015-10-26 22:33:06
Also in: linux-efi

On 10/26/2015 05:26 PM, Jeremy Linton wrote:
On 10/08/2015 02:02 PM, Ard Biesheuvel wrote:
quoted
Since arm64 does not use a builtin decompressor, the EFI stub is built
into the kernel proper. So far, this has been working fine, but actually,
since the stub is in fact a PE/COFF relocatable binary that is executed
at an unknown offset in the 1:1 mapping provided by the UEFI firmware, we
should not be seamlessly sharing code with the kernel proper, which is a
position dependent executable linked at a high virtual offset.
This patch appears to be causing a build break

  STUBCPY drivers/firmware/efi/libstub/lib-sort.stub.o
0000000000000000 R_AARCH64_ABS64   __efistub___crc_sort
drivers/firmware/efi/libstub/lib-sort.stub.o: absolute symbol references
not allowed in the EFI stub

__kcrctab_sort:
     .xword    __crc_sort
     .weak    __crc_sort
     .text


Which is the EXPORT_SYMBOL() in sort.c combined with !CONFIG_MODVERSIONS.
	Sorry, I that should be CONFIG_MODVERSIONS..
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help