summaryrefslogtreecommitdiff
path: root/drivers/irqchip
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2018-09-14 11:14:11 +1000
committerMichael Ellerman <mpe@ellerman.id.au>2018-09-18 22:42:54 +1000
commit51c3c62b58b357e8d35e4cc32f7b4ec907426fe3 (patch)
treeb11eefccbfe4df8cc01511fb81b7caf7a23d790e /drivers/irqchip
parentf14040bca89258b8a1c71e2112e430462172ce93 (diff)
powerpc: Avoid code patching freed init sections
This stops us from doing code patching in init sections after they've been freed. In this chain: kvm_guest_init() -> kvm_use_magic_page() -> fault_in_pages_readable() -> __get_user() -> __get_user_nocheck() -> barrier_nospec(); We have a code patching location at barrier_nospec() and kvm_guest_init() is an init function. This whole chain gets inlined, so when we free the init section (hence kvm_guest_init()), this code goes away and hence should no longer be patched. We seen this as userspace memory corruption when using a memory checker while doing partition migration testing on powervm (this starts the code patching post migration via /sys/kernel/mobility/migration). In theory, it could also happen when using /sys/kernel/debug/powerpc/barrier_nospec. Cc: stable@vger.kernel.org # 4.13+ Signed-off-by: Michael Neuling <mikey@neuling.org> Reviewed-by: Nicholas Piggin <npiggin@gmail.com> Reviewed-by: Christophe Leroy <christophe.leroy@c-s.fr> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'drivers/irqchip')
0 files changed, 0 insertions, 0 deletions