LoongArch: Fix oops during single-step debugging
PATCH 1/1 LoongArch: Fix oops during single-step debugging
From: Haoran Jiang <[email protected]>
When entering KDB via a breakpoint and then performing single-step debugging,an oops is triggered.During single-step debugging, kdb_local() expects the reason to be KDB_REASON_SSTEP, but it is actually KDB_REASON_OOPS. In kdb_stub(), when determining the reason, the ex_vector for single-step should be 0, as already implemented on other architectures such as arm64 and riscv.
Before the patch:
[112]kdb> ss
Entering kdb (current=0x900020009f520000, pid 10661) on processor 112 Oops: (null)
due to oops @ 0x90000000005b57a4
Signed-off-by Haoran Jiang <[email protected]>
--- arch/loongarch/kernel/kgdb.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/loongarch/kernel/kgdb.c +2 -1
@@ -252,7 +252,8 @@ static int kgdb_loongarch_notify(struct notifier_block *self, unsigned long cmd,if (atomic_read (&kgdb_active) !=-1 )kgdb_nmicallback (smp_processor_id (), regs); -if (kgdb_handle_exception (args->trapnr, args->signr, cmd, regs)) +if (kgdb_handle_exception ((regs->csr_era == stepped_address ?0 : args->trapnr), + args->signr, cmd, regs))return NOTIFY_DONE ;if (atomic_read (&kgdb_setting_breakpoint))
Signature · 1 line
2.43.0