summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWill Deacon <will.deacon@arm.com>2014-04-17 12:37:14 +0100
committerCatalin Marinas <catalin.marinas@arm.com>2014-04-25 16:46:50 +0100
commit43683afbcb32f7b7318ac1badd6469d91fe22711 (patch)
tree7278aa89b4da8148393092d5944b45284a0a2590
parent2eb835e058c737205d35d9a8791ad27b0f9e89a4 (diff)
downloadlinux-43683afbcb32f7b7318ac1badd6469d91fe22711.tar.gz
linux-43683afbcb32f7b7318ac1badd6469d91fe22711.tar.bz2
linux-43683afbcb32f7b7318ac1badd6469d91fe22711.zip
arm64: debug: remove noisy, pointless warning
Sending a SIGTRAP to a user task after execution of a BRK instruction at EL0 is fundamental to the way in which software breakpoints work and doesn't deserve a warning to be logged in dmesg. Whilst the warning can be justified from EL1, do_debug_exception will already do the right thing, so simply remove the code altogether. Cc: Sandeepa Prabhu <sandeepa.prabhu@linaro.org> Reported-by: Kyrylo Tkachov <kyrylo.tkachov@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
-rw-r--r--arch/arm64/kernel/debug-monitors.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/arch/arm64/kernel/debug-monitors.c b/arch/arm64/kernel/debug-monitors.c
index ed3955a95747..a7fb874b595e 100644
--- a/arch/arm64/kernel/debug-monitors.c
+++ b/arch/arm64/kernel/debug-monitors.c
@@ -318,9 +318,6 @@ static int brk_handler(unsigned long addr, unsigned int esr,
if (call_break_hook(regs, esr) == DBG_HOOK_HANDLED)
return 0;
- pr_warn("unexpected brk exception at %lx, esr=0x%x\n",
- (long)instruction_pointer(regs), esr);
-
if (!user_mode(regs))
return -EFAULT;