powerpc/mm: Don't be too strict with _etext alignment on PPC32
authorChristophe Leroy <christophe.leroy@csgroup.eu>
Tue, 19 May 2020 05:49:19 +0000 (05:49 +0000)
committerMichael Ellerman <mpe@ellerman.id.au>
Tue, 26 May 2020 12:22:22 +0000 (22:22 +1000)
commita0591b60eef965f7f5255ad4696bbba9af4b43d0
tree22cfa6ca4e51f9fab66d544f6e6d9df2fbe9219b
parent0c8c2c9c201b44eed6c10d7c5c8d25fe5aab87ce
powerpc/mm: Don't be too strict with _etext alignment on PPC32

Similar to PPC64, accept to map RO data as ROX as a trade off between
between security and memory usage.

Having RO data executable is not a high risk as RO data can't be
modified to forge an exploit.

Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/8c4a0d89d944eed984dd941e509614031a5ace2b.1589866984.git.christophe.leroy@csgroup.eu
arch/powerpc/Kconfig
arch/powerpc/kernel/vmlinux.lds.S