From: Thomas Garnier <thgarnie@chromium.org>
To: kernel-hardening@lists.openwall.com
Cc: kristen@linux.intel.com, keescook@chromium.org,
Thomas Garnier <thgarnie@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v10 02/11] x86: Add macro to get symbol address for PIE support
Date: Wed, 4 Dec 2019 16:09:39 -0800 [thread overview]
Message-ID: <20191205000957.112719-3-thgarnie@chromium.org> (raw)
In-Reply-To: <20191205000957.112719-1-thgarnie@chromium.org>
Add a new _ASM_MOVABS macro to fetch a symbol address. Replace
"_ASM_MOV $<symbol>, %dst" code construct that are not compatible with
PIE.
Signed-off-by: Thomas Garnier <thgarnie@chromium.org>
---
arch/x86/include/asm/asm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/asm.h b/arch/x86/include/asm/asm.h
index cd339b88d5d4..644bdbf149ee 100644
--- a/arch/x86/include/asm/asm.h
+++ b/arch/x86/include/asm/asm.h
@@ -32,6 +32,7 @@
#define _ASM_ALIGN __ASM_SEL(.balign 4, .balign 8)
#define _ASM_MOV __ASM_SIZE(mov)
+#define _ASM_MOVABS __ASM_SEL(movl, movabsq)
#define _ASM_INC __ASM_SIZE(inc)
#define _ASM_DEC __ASM_SIZE(dec)
#define _ASM_ADD __ASM_SIZE(add)
--
2.24.0.393.g34dc348eaf-goog
next prev parent reply other threads:[~2019-12-05 0:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 0:09 [PATCH v10 00/11] x86: PIE support to extend KASLR randomization Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 01/11] x86/crypto: Adapt assembly for PIE support Thomas Garnier
2019-12-18 12:46 ` Borislav Petkov
2019-12-18 16:35 ` Thomas Garnier
2019-12-18 16:45 ` Borislav Petkov
2019-12-05 0:09 ` Thomas Garnier [this message]
2019-12-05 0:09 ` [PATCH v10 03/11] x86: relocate_kernel - " Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 04/11] x86/entry/64: " Thomas Garnier
2019-12-05 9:03 ` Peter Zijlstra
2019-12-05 17:01 ` Thomas Garnier
2019-12-06 10:26 ` Peter Zijlstra
2019-12-06 16:35 ` Thomas Garnier
2019-12-20 16:05 ` Borislav Petkov
2019-12-05 0:09 ` [PATCH v10 05/11] x86: pm-trace - " Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 06/11] x86/CPU: " Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 07/11] x86/acpi: " Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 08/11] x86/boot/64: " Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 09/11] x86/power/64: " Thomas Garnier
2019-12-05 0:09 ` [PATCH v10 10/11] x86/paravirt: " Thomas Garnier
2019-12-23 17:23 ` Borislav Petkov
2019-12-24 10:04 ` Borislav Petkov
2019-12-05 0:09 ` [PATCH v10 11/11] x86/alternatives: " Thomas Garnier
2019-12-19 13:34 ` [PATCH v10 00/11] x86: PIE support to extend KASLR randomization Peter Zijlstra
2019-12-19 16:35 ` Thomas Garnier
2019-12-24 13:03 ` Borislav Petkov
2019-12-30 18:52 ` 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=20191205000957.112719-3-thgarnie@chromium.org \
--to=thgarnie@chromium.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.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).