From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm/arm64: localise objcopy flags
Date: Tue, 12 Jul 2016 16:28:00 +0100 [thread overview]
Message-ID: <1468337282-14527-1-git-send-email-mark.rutland@arm.com> (raw)
Hi,
Typically, architectures (including arm and arm64) define OBJCOPYFLAGS in their
top-level makefile, for the purpose of generating a raw binaries suitable for
booting, including Image, zImage, vmlinux.bin, etc.
As this top-level arch makefile is included by the top-level kernel makefile,
these flags are passed to other invocations of objcopy tree-wide. This can
result in unexpected and inconsistent behaviour across architectures (e.g.
generation of a raw binary rather than an ELF [1]).
Rather than force each new user of objcopy to specially clear OBJCOPYFLAGS,
this patch moves the existing OBJCOPYFLAGS variable definitions such that they
only affects the cases we require them for today, leaving the global namespace
clear.
Other architectures will likely need similar treatment.
Thanks,
Mark.
[1] http://www.openwall.com/lists/kernel-hardening/2016/06/08/2
Mark Rutland (2):
arm64: localise Image objcopy flags
arm: localise objcopy flags
arch/arm/Makefile | 1 -
arch/arm/boot/Makefile | 2 ++
arch/arm64/Makefile | 1 -
arch/arm64/boot/Makefile | 2 ++
4 files changed, 4 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2016-07-12 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 15:28 Mark Rutland [this message]
2016-07-12 15:28 ` [PATCH 1/2] arm64: localise Image objcopy flags Mark Rutland
2016-07-12 15:28 ` [PATCH 2/2] arm: localise " Mark Rutland
2016-07-12 17:03 ` [PATCH 0/2] arm/arm64: " Kees Cook
2016-07-18 23:16 ` Laura Abbott
2016-07-19 10:29 ` Mark Rutland
2016-07-19 14:31 ` Catalin Marinas
2016-07-19 14:35 ` 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=1468337282-14527-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--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).