The kgdb_single_step flag has the possibility to indefinitely
hang the system on an SMP system.
The x86 arch have the same problem, and that problem was fixed by
commit 8097551d9ab9b9e3630(kgdb,x86: do not set kgdb_single_step
on x86). This patch does the same behaviors as x86's patch.
Signed-off-by: Dongdong Deng <redacted>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Tiejun Chen <redacted>
---
arch/powerpc/kernel/kgdb.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
@@ -410,7 +410,6 @@ int kgdb_arch_handle_exception(int vector, int signo, int err_code,#elselinux_regs->msr|=MSR_SE;#endif-kgdb_single_step=1;atomic_set(&kgdb_cpu_doing_single_step,raw_smp_processor_id());}
For powerpc BooKE and e200, singlestep is handled on the critical/dbg
exception stack. This causes current_thread_info() to fail for kgdb
internal, so previously We work around this issue by copying
the thread_info from the kernel stack before calling kgdb_handle_exception,
and copying it back afterwards.
But actually we don't do this previously. We should backp current_thread_info
then restore that when exit.
CC: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Tiejun Chen <redacted>
---
arch/powerpc/kernel/kgdb.c | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
@@ -156,6 +157,8 @@ static int kgdb_handle_breakpoint(struct pt_regs *regs)staticintkgdb_singlestep(structpt_regs*regs){structthread_info*thread_info,*exception_thread_info;+structthread_info*backup_current_thread_info=\+(structthread_info*)kmalloc(sizeof(structthread_info),GFP_KERNEL);if(user_mode(regs))return0;
@@ -173,13 +176,17 @@ static int kgdb_singlestep(struct pt_regs *regs)thread_info=(structthread_info*)(regs->gpr[1]&~(THREAD_SIZE-1));exception_thread_info=current_thread_info();-if(thread_info!=exception_thread_info)+if(thread_info!=exception_thread_info){+/* Save the original current_thread_info. */+memcpy(backup_current_thread_info,exception_thread_info,sizeof*thread_info);memcpy(exception_thread_info,thread_info,sizeof*thread_info);+}kgdb_handle_exception(0,SIGTRAP,0,regs);if(thread_info!=exception_thread_info)-memcpy(thread_info,exception_thread_info,sizeof*thread_info);+/* Restore current_thread_info lastly. */+memcpy(exception_thread_info,backup_current_thread_info,sizeof*thread_info);return1;}
We need to skip a breakpoint exception when it occurs after
a breakpoint has already been removed.
Signed-off-by: Tiejun Chen <redacted>
---
arch/powerpc/kernel/kgdb.c | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
@@ -101,6 +101,24 @@ static int computeSignal(unsigned int tt)returnSIGHUP;/* default for things we don't know about */}+/**+*+*kgdb_skipexception-BailoutofKGDBwhenwe'vebeentriggered.+*@exception:Exceptionvectornumber+*@regs:Current&structpt_regs.+*+*Onsomearchitecturesweneedtoskipabreakpointexceptionwhen+*itoccursafterabreakpointhasbeenremoved.+*+*/+intkgdb_skipexception(intexception,structpt_regs*regs)+{+if(kgdb_isremovedbreak(regs->nip))+return1;++return0;+}+staticintkgdb_call_nmi_hook(structpt_regs*regs){kgdb_nmicallback(raw_smp_processor_id(),regs);
int kgdb_skipexception(int exception, struct pt_regs *regs)
{
return !!kgdb_isremovedbreak(regs->nip));
}
If the caller only cares about zero vs. non-zero, you can drop the !!.
--=20
Timur Tabi
Linux kernel developer at Freescale=
int kgdb_skipexception(int exception, struct pt_regs *regs)
{
return !!kgdb_isremovedbreak(regs->nip));
}
If the caller only cares about zero vs. non-zero, you can drop the !!.
Yes, so 'return kgdb_isremovedbreak(regs->nip);' is already fine and simple.
I'll update this as v2 so thanks your comment.
Tiejun