diff options
author | Masami Hiramatsu <mhiramat@kernel.org> | 2017-02-14 00:03:38 +0900 |
---|---|---|
committer | Jon Medhurst <tixy@linaro.org> | 2017-03-21 16:24:18 +0000 |
commit | f3fbd7ec62dec1528fb8044034e2885f2b257941 (patch) | |
tree | 5e14e41e31c5716f061c3c6b04c5d333880b5b3c /arch/arm/mach-mediatek | |
parent | 4495c08e84729385774601b5146d51d9e5849f81 (diff) | |
download | linux-f3fbd7ec62dec1528fb8044034e2885f2b257941.tar.bz2 |
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>
Diffstat (limited to 'arch/arm/mach-mediatek')
0 files changed, 0 insertions, 0 deletions