From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com
Subject: Re: powerpc/mm/radix: Only add X for pages overlapping kernel text
Date: Mon, 19 Jun 2017 22:25:36 +1000 (AEST) [thread overview]
Message-ID: <3wrqv42DRXz9s89@ozlabs.org> (raw)
In-Reply-To: <1496728137-19655-1-git-send-email-mpe@ellerman.id.au>
On Tue, 2017-06-06 at 05:48:57 UTC, Michael Ellerman wrote:
> Currently we map the whole linear mapping with PAGE_KERNEL_X. Instead we
> should check if the page overlaps the kernel text and only then add
> PAGE_KERNEL_X.
>
> Note that we still use 1G pages if they're available, so this will
> typically still result in a 1G executable page at KERNELBASE. So this fix is
> primarily useful for catching stray branches to high linear mapping addresses.
>
> Without this patch, we can execute at 1G in xmon using:
>
> 0:mon> m c000000040000000
> c000000040000000 00 l
> c000000040000000 00000000 01006038
> c000000040000004 00000000 2000804e
> c000000040000008 00000000 x
> 0:mon> di c000000040000000
> c000000040000000 38600001 li r3,1
> c000000040000004 4e800020 blr
> 0:mon> p c000000040000000
> return value is 0x1
>
> After we get a 400 as expected:
>
> 0:mon> p c000000040000000
> *** 400 exception occurred
>
> Fixes: 2bfd65e45e87 ("powerpc/mm/radix: Add radix callbacks for early init routines")
> Cc: stable@vger.kernel.org # v4.7+
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Acked-by: Balbir Singh <bsingharora@gmail.com>
Applied to powerpc next.
https://git.kernel.org/powerpc/c/9abcc981de9775659a0f6e4a52a344
cheers
prev parent reply other threads:[~2017-06-19 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 5:48 [PATCH] powerpc/mm/radix: Only add X for pages overlapping kernel text Michael Ellerman
2017-06-06 6:03 ` Balbir Singh
2017-06-06 10:17 ` Michael Ellerman
2017-06-08 7:49 ` Balbir Singh
2017-06-08 7:00 ` Aneesh Kumar K.V
2017-06-19 12:25 ` Michael Ellerman [this message]
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=3wrqv42DRXz9s89@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--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).