diff options
author | Balbir Singh <bsingharora@gmail.com> | 2017-06-28 20:04:10 +0300 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-07-03 16:12:19 +0300 |
commit | 7f6d498ed3354740cfd100e4aa99e388f1a95be7 (patch) | |
tree | 17d58e5484a9b97a1c442a70681abedafa573006 /firmware/atmsar11.HEX | |
parent | e71ff982ae4c17d176e9f0132157d54973788377 (diff) | |
download | linux-7f6d498ed3354740cfd100e4aa99e388f1a95be7.tar.xz |
powerpc/mm/radix: Fix execute permissions for interrupt_vectors
Commit 9abcc981de97 ("powerpc/mm/radix: Only add X for pages
overlapping kernel text") changed the linear mapping on Radix to only
mark the kernel text executable.
However if the kernel is run relocated, for example as a kdump kernel,
then the exception vectors are split from the kernel text, ie. they
remain at real address 0.
We tend to get away with it, because the kernel itself will usually be
below 1G, which means the 1G page at 0-1G is marked executable and
everything works OK. However if the kernel is loaded above 1G, or the
system has less than 1G in total (meaning we can't use a 1G page),
then the exception vectors will not be marked executable and the
kernel will fail to boot.
Fix it by also checking if the address range overlaps the exception
vectors when deciding if we should add PAGE_KERNEL_X.
Fixes: 9abcc981de97 ("powerpc/mm/radix: Only add X for pages overlapping kernel text")
Cc: stable@vger.kernel.org # v4.7+
Signed-off-by: Balbir Singh <bsingharora@gmail.com>
[mpe: Combine with the existing check, rewrite change log]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'firmware/atmsar11.HEX')
0 files changed, 0 insertions, 0 deletions