From: tip-bot for Michael Davidson <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
keescook@chromium.org, md@google.com, tglx@linutronix.de,
hpa@linux.intel.com
Subject: [tip:x86/kaslr] x86, relocs: Add more per-cpu gold special cases
Date: Sun, 13 Oct 2013 05:01:08 -0700 [thread overview]
Message-ID: <tip-d751c169e9a6f0f853346f1184881422bd10b3c2@git.kernel.org> (raw)
In-Reply-To: <20131011013954.GA28902@www.outflux.net>
Commit-ID: d751c169e9a6f0f853346f1184881422bd10b3c2
Gitweb: http://git.kernel.org/tip/d751c169e9a6f0f853346f1184881422bd10b3c2
Author: Michael Davidson <md@google.com>
AuthorDate: Thu, 10 Oct 2013 18:39:54 -0700
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Sun, 13 Oct 2013 03:11:57 -0700
x86, relocs: Add more per-cpu gold special cases
The "gold" linker doesn't seem to put some additional per-cpu cases in
the right place. Add these to the per-cpu check. Without this, the kASLR
patch series fails to correctly apply relocations, and fails to boot.
Signed-off-by: Michael Davidson <md@google.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: http://lkml.kernel.org/r/20131011013954.GA28902@www.outflux.net
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
arch/x86/tools/relocs.c | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/arch/x86/tools/relocs.c b/arch/x86/tools/relocs.c
index f7bab68..71a2533 100644
--- a/arch/x86/tools/relocs.c
+++ b/arch/x86/tools/relocs.c
@@ -722,15 +722,23 @@ static void percpu_init(void)
/*
* Check to see if a symbol lies in the .data..percpu section.
- * For some as yet not understood reason the "__init_begin"
- * symbol which immediately preceeds the .data..percpu section
- * also shows up as it it were part of it so we do an explict
- * check for that symbol name and ignore it.
+ *
+ * The linker incorrectly associates some symbols with the
+ * .data..percpu section so we also need to check the symbol
+ * name to make sure that we classify the symbol correctly.
+ *
+ * The GNU linker incorrectly associates:
+ * __init_begin
+ *
+ * The "gold" linker incorrectly associates:
+ * init_per_cpu__irq_stack_union
+ * init_per_cpu__gdt_page
*/
static int is_percpu_sym(ElfW(Sym) *sym, const char *symname)
{
return (sym->st_shndx == per_cpu_shndx) &&
- strcmp(symname, "__init_begin");
+ strcmp(symname, "__init_begin") &&
+ strncmp(symname, "init_per_cpu_", 13);
}
next prev parent reply other threads:[~2013-10-13 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 1:39 [PATCH v2] x86, relocs: add more per-cpu gold special cases Kees Cook
2013-10-13 12:01 ` tip-bot for Michael Davidson [this message]
2013-10-14 8:30 ` [tip:x86/kaslr] x86, relocs: Add " Ingo Molnar
2013-10-14 9:38 ` Ingo Molnar
2013-10-14 14:19 ` H. Peter Anvin
2013-10-14 16:28 ` H. Peter Anvin
2013-10-14 20:47 ` Kees Cook
2013-10-15 6:04 ` Ingo Molnar
2013-10-15 15:42 ` Kees Cook
2013-10-15 16:03 ` Ingo Molnar
2013-10-15 17:22 ` Kees Cook
2013-10-16 6:56 ` Ingo Molnar
2013-10-16 14:53 ` Kees Cook
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=tip-d751c169e9a6f0f853346f1184881422bd10b3c2@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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).