From: Anton Blanchard <anton@samba.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Ensure .mem(init|exit).text are within _stext/_etext
Date: Thu, 15 Sep 2016 15:28:32 +1000 [thread overview]
Message-ID: <20160915152832.0f1a6708@kryten> (raw)
In-Reply-To: <1473916319-27736-1-git-send-email-mpe@ellerman.id.au>
Hi,
> In our linker script we open code the list of text sections, because
> we need to include the __ftr_alt sections, which are arch-specific.
>
> This means we can't use TEXT_TEXT as defined in vmlinux.lds.h, and so
> we don't have the MEM_KEEP() logic for memory hotplug sections.
>
> If we build the kernel with the gold linker, and with
> CONFIG_MEMORY_HOTPLUG=y, we see that functions marked __meminit can
> end up outside of the _stext/_etext range, and also outside of
> _sinittext/_einittext, eg:
>
> c000000000000000 T _stext
> c0000000009e0000 A _etext
> c0000000009e3f18 T hash__vmemmap_create_mapping
> c000000000ca0000 T _sinittext
> c000000000d00844 T _einittext
>
> This causes them to not be recognised as text by is_kernel_text(), and
> prevents them being patched by jump_label (and presumably
> ftrace/kprobes etc.).
>
> Fix it by adding MEM_KEEP() directives, mirroring what TEXT_TEXT does.
>
> This isn't a problem when CONFIG_MEMORY_HOTPLUG=n, because we use the
> standard INIT_TEXT_SECTION() and EXIT_TEXT macros from vmlinux.lds.h.
Thanks Michael, looks good:
Tested-by: Anton Blanchard <anton@samba.org>
Anton
--
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> arch/powerpc/kernel/vmlinux.lds.S | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/powerpc/kernel/vmlinux.lds.S
> b/arch/powerpc/kernel/vmlinux.lds.S index b5fba689fca6..b59d75e194a5
> 100644 --- a/arch/powerpc/kernel/vmlinux.lds.S
> +++ b/arch/powerpc/kernel/vmlinux.lds.S
> @@ -56,6 +56,8 @@ SECTIONS
> KPROBES_TEXT
> IRQENTRY_TEXT
> SOFTIRQENTRY_TEXT
> + MEM_KEEP(init.text)
> + MEM_KEEP(exit.text)
>
> #ifdef CONFIG_PPC32
> *(.got1)
next prev parent reply other threads:[~2016-09-15 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 5:11 [PATCH] powerpc: Ensure .mem(init|exit).text are within _stext/_etext Michael Ellerman
2016-09-15 5:28 ` Anton Blanchard [this message]
2016-09-20 13:07 ` Michael Ellerman
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=20160915152832.0f1a6708@kryten \
--to=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).