riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
authorVincent Chen <vincent.chen@sifive.com>
Mon, 23 Sep 2019 00:45:15 +0000 (08:45 +0800)
committerPaul Walmsley <paul.walmsley@sifive.com>
Mon, 7 Oct 2019 19:59:40 +0000 (12:59 -0700)
commite0c0fc18f10d5080cddde0e81505fd3e952c20c4
treedeb30fecb20f23a85088c3c8da3d026cbef63b88
parent8b04825ed205da38754f86f4c07ea8600d8c2a65
riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()

On RISC-V, when the kernel runs code on behalf of a user thread, and the
kernel executes a WARN() or WARN_ON(), the user thread will be sent
a bogus SIGTRAP.  Fix the RISC-V kernel code to not send a SIGTRAP when
a WARN()/WARN_ON() is executed.

Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
[paul.walmsley@sifive.com: fixed subject]
Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
arch/riscv/kernel/traps.c