]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
powerpc/64s/interrupt: Fix check_return_regs_valid() false positive
authorNicholas Piggin <npiggin@gmail.com>
Tue, 26 Oct 2021 12:25:31 +0000 (22:25 +1000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 17 Nov 2021 10:04:50 +0000 (11:04 +0100)
commitbaf19ea102c3f3712fa9c5fef8a6ca3d37a90c1a
tree106e0654b8c4928413f149a4102d2981d9e0e768
parent251959e47018b4696ccbef32f5502f0f810603f4
powerpc/64s/interrupt: Fix check_return_regs_valid() false positive

commit 4a5cb51f3db4be547225a4bce7a43d41b231382b upstream.

The check_return_regs_valid() can cause a false positive if the return
regs are marked as norestart and they are an HSRR type interrupt,
because the low bit in the bottom of regs->trap causes interrupt type
matching to fail.

This can occcur for example on bare metal with a HV privileged doorbell
interrupt that causes a signal, but do_signal returns early because
get_signal() fails, and takes the "No signal to deliver" path. In this
case no signal was delivered so the return location is not changed so
return SRRs are not invalidated, yet set_trap_norestart is called, which
messes up the match. Building go-1.16.6 is known to reproduce this.

Fix it by using the TRAP() accessor which masks out the low bit.

Fixes: 6eaaf9de3599 ("powerpc/64s/interrupt: Check and fix srr_valid without crashing")
Cc: stable@vger.kernel.org # v5.14+
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20211026122531.3599918-1-npiggin@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/powerpc/kernel/interrupt.c