From: Balbir Singh <bsingharora@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au
Cc: naveen.n.rao@linux.vnet.ibm.com, christophe.leroy@c-s.fr,
paulus@samba.org, rashmica.g@gmail.com, labbott@redhat.com,
Balbir Singh <bsingharora@gmail.com>
Subject: [PATCH v2 5/9] powerpc/vmlinux.lds: Align __init_begin to 16M
Date: Sat, 3 Jun 2017 17:18:39 +1000 [thread overview]
Message-ID: <20170603071843.11966-6-bsingharora@gmail.com> (raw)
In-Reply-To: <20170603071843.11966-1-bsingharora@gmail.com>
For CONFIG_STRICT_KERNEL_RWX align __init_begin to 16M.
We use 16M since its the larger of 2M on radix and 16M
on hash for our linear mapping. The plan is to have
.text, .rodata and everything upto __init_begin marked
as RX. Note we still have executable read only data.
We could further align read only data to another 16M
boundary, but then the linker starts using stubs and
that breaks our assembler code in head_64.S
We don't use multi PT_LOAD in PHDRS because we are
not sure if all bootloaders support them
Signed-off-by: Balbir Singh <bsingharora@gmail.com>
---
arch/powerpc/kernel/vmlinux.lds.S | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/vmlinux.lds.S b/arch/powerpc/kernel/vmlinux.lds.S
index ace6b65..b1a2505 100644
--- a/arch/powerpc/kernel/vmlinux.lds.S
+++ b/arch/powerpc/kernel/vmlinux.lds.S
@@ -8,6 +8,12 @@
#include <asm/cache.h>
#include <asm/thread_info.h>
+#ifdef CONFIG_STRICT_KERNEL_RWX
+#define STRICT_ALIGN_SIZE (1 << 24)
+#else
+#define STRICT_ALIGN_SIZE PAGE_SIZE
+#endif
+
ENTRY(_stext)
PHDRS {
@@ -123,7 +129,7 @@ SECTIONS
PROVIDE32 (etext = .);
/* Read-only data */
- RODATA
+ RO_DATA(PAGE_SIZE)
EXCEPTION_TABLE(0)
@@ -140,7 +146,7 @@ SECTIONS
/*
* Init sections discarded at runtime
*/
- . = ALIGN(PAGE_SIZE);
+ . = ALIGN(STRICT_ALIGN_SIZE);
__init_begin = .;
INIT_TEXT_SECTION(PAGE_SIZE) :kernel
--
2.9.3
next prev parent reply other threads:[~2017-06-03 7:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 7:18 [PATCH v2 0/9] Enable STRICT_KERNEL_RWX Balbir Singh
2017-06-03 7:18 ` [PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching Balbir Singh
2017-06-03 23:45 ` kbuild test robot
2017-06-07 10:25 ` Christophe LEROY
2017-06-07 11:04 ` Balbir Singh
2017-06-07 11:52 ` Michael Ellerman
2017-06-03 7:18 ` [PATCH v2 2/9] powerpc/kprobes: Move kprobes over to patch_instruction Balbir Singh
2017-06-03 7:18 ` [PATCH v2 3/9] powerpc/kprobes/optprobes: Move " Balbir Singh
2017-06-03 7:18 ` [PATCH v2 4/9] powerpc/xmon: Add patch_instruction supporf for xmon Balbir Singh
2017-06-03 7:18 ` Balbir Singh [this message]
2017-06-04 4:22 ` [PATCH v2 5/9] powerpc/vmlinux.lds: Align __init_begin to 16M Nicholas Piggin
2017-06-04 22:42 ` Balbir Singh
2017-06-05 6:51 ` Nicholas Piggin
2017-06-03 7:18 ` [PATCH v2 6/9] powerpc/platform/pseries/lpar: Fix updatepp and updateboltedpp Balbir Singh
2017-06-03 7:18 ` [PATCH v2 7/9] powerpc/mm/hash: Implement mark_rodata_ro() for hash Balbir Singh
2017-06-03 7:18 ` [PATCH v2 8/9] powerpc/Kconfig: Enable STRICT_KERNEL_RWX Balbir Singh
2017-06-03 7:18 ` [PATCH v2 9/9] powerpc/mm/ptdump: Dump the first entry of the linear mapping as well Balbir Singh
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=20170603071843.11966-6-bsingharora@gmail.com \
--to=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=labbott@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=rashmica.g@gmail.com \
/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).