public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: jeremy.linton@arm•com (Jeremy Linton)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 3/3] arm64/efi: isolate EFI stub from the kernel proper
Date: Mon, 26 Oct 2015 17:33:06 -0500	[thread overview]
Message-ID: <562EAA22.3010905@arm.com> (raw)
In-Reply-To: <562EA894.8070505@arm.com>

On 10/26/2015 05:26 PM, Jeremy Linton wrote:
> On 10/08/2015 02:02 PM, Ard Biesheuvel wrote:
>> 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..

  reply	other threads:[~2015-10-26 22:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 19:02 [PATCH v4 0/3] arm64: EFI stub isolation Ard Biesheuvel
2015-10-08 19:02 ` [PATCH v4 1/3] arm64/efi: remove /chosen/linux, uefi-stub-kern-ver DT property Ard Biesheuvel
2015-10-10 22:31   ` [PATCH v4 1/3] arm64/efi: remove /chosen/linux,uefi-stub-kern-ver " Matt Fleming
2015-10-08 19:02 ` [PATCH v4 2/3] arm64: use ENDPIPROC() to annotate position independent assembler routines Ard Biesheuvel
2015-10-08 19:02 ` [PATCH v4 3/3] arm64/efi: isolate EFI stub from the kernel proper Ard Biesheuvel
2015-10-09  8:12   ` Andrey Ryabinin
2015-10-09  9:10     ` Will Deacon
2015-10-09  9:40       ` Andrey Ryabinin
2015-10-09  9:43         ` Will Deacon
2015-10-09  9:48           ` Andrey Ryabinin
2015-10-10 22:40   ` Matt Fleming
2015-10-26 22:26   ` Jeremy Linton
2015-10-26 22:33     ` Jeremy Linton [this message]
2015-10-27  2:20       ` Ard Biesheuvel
2015-10-27 14:44         ` Jeremy Linton
2015-10-30 12:17           ` Ard Biesheuvel
2015-10-30 14:35             ` Mark Rutland
2015-10-30 16:01             ` Catalin Marinas
2015-11-02 12:49         ` Matt Fleming
2015-11-24  9:34   ` Robert Richter
2015-11-24  9:38     ` Ard Biesheuvel
2015-10-10 22:40 ` [PATCH v4 0/3] arm64: EFI stub isolation Matt Fleming
2015-10-12 15:30   ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=562EAA22.3010905@arm.com \
    --to=jeremy.linton@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox