From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] efi: arm64: use -fpie for building the stub
Date: Thu, 18 May 2017 10:09:50 +0100 [thread overview]
Message-ID: <20170518090953.32628-1-ard.biesheuvel@linaro.org> (raw)
Clang requires the stub to be built with -fpie, or it may emit absolute
symbol references that trigger the absolute relocation detection code and
cause the build to fail.
The remedy is to set -fpie (#3), but due to stupid ELF symbol preemption
rules that only apply to shared libraries, this will result in more rather
than fewer absolute references (i.e., GOT entries), which we have to massage
away using visibility overrides first. (#1, #2)
Ard Biesheuvel (3):
efi/libstub: arm64: use hidden attribute for struct screen_info
reference
efi/libstub: arm64: force 'hidden' visibility for section markers
efi/libstub: arm64: set -fpie when building the EFI stub
arch/arm64/include/asm/efi.h | 3 +++
drivers/firmware/efi/libstub/Makefile | 2 +-
drivers/firmware/efi/libstub/arm64-stub.c | 10 +++++++++-
3 files changed, 13 insertions(+), 2 deletions(-)
--
2.9.3
next reply other threads:[~2017-05-18 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:09 Ard Biesheuvel [this message]
2017-05-18 9:09 ` [PATCH 1/3] efi/libstub: arm64: use hidden attribute for struct screen_info reference Ard Biesheuvel
2017-06-08 19:06 ` Matthias Kaehlcke
2017-05-18 9:09 ` [PATCH 2/3] efi/libstub: arm64: force 'hidden' visibility for section markers Ard Biesheuvel
2017-06-08 19:07 ` Matthias Kaehlcke
2017-05-18 9:09 ` [PATCH 3/3] efi/libstub: arm64: set -fpie when building the EFI stub Ard Biesheuvel
2017-06-08 19:08 ` Matthias Kaehlcke
2017-06-08 19:18 ` Ard Biesheuvel
2017-06-08 19:44 ` Matthias Kaehlcke
2017-06-09 9:02 ` [PATCH 0/3] efi: arm64: use -fpie for building the stub Ard Biesheuvel
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=20170518090953.32628-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).