arm: kprobes: Allow to handle reentered kprobe on single-stepping

This is arm port of commit 6a5022a56ac3 ("kprobes/x86: Allow to
handle reentered kprobe on single-stepping")

Since the FIQ handlers can interrupt in the single stepping
(or preparing the single stepping, do_debug etc.), we should
consider a kprobe is hit in the NMI handler. Even in that
case, the kprobe is allowed to be reentered as same as the
kprobes hit in kprobe handlers
(KPROBE_HIT_ACTIVE or KPROBE_HIT_SSDONE).

The real issue will happen when a kprobe hit while another
reentered kprobe is processing (KPROBE_REENTER), because
we already consumed a saved-area for the previous kprobe.

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Jon Medhurst <tixy@linaro.org>

authored by Masami Hiramatsu and committed by Jon Medhurst f3fbd7ec 4495c08e

+6
+6
arch/arm/probes/kprobes/core.c
··· 271 switch (kcb->kprobe_status) { 272 case KPROBE_HIT_ACTIVE: 273 case KPROBE_HIT_SSDONE: 274 /* A pre- or post-handler probe got us here. */ 275 kprobes_inc_nmissed_count(p); 276 save_previous_kprobe(kcb); ··· 280 singlestep(p, regs, kcb); 281 restore_previous_kprobe(kcb); 282 break; 283 default: 284 /* impossible cases */ 285 BUG();
··· 271 switch (kcb->kprobe_status) { 272 case KPROBE_HIT_ACTIVE: 273 case KPROBE_HIT_SSDONE: 274 + case KPROBE_HIT_SS: 275 /* A pre- or post-handler probe got us here. */ 276 kprobes_inc_nmissed_count(p); 277 save_previous_kprobe(kcb); ··· 279 singlestep(p, regs, kcb); 280 restore_previous_kprobe(kcb); 281 break; 282 + case KPROBE_REENTER: 283 + /* A nested probe was hit in FIQ, it is a BUG */ 284 + pr_warn("Unrecoverable kprobe detected at %p.\n", 285 + p->addr); 286 + /* fall through */ 287 default: 288 /* impossible cases */ 289 BUG();