[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210708124240.20048-1-huangshaobo6@huawei.com>
Date: Thu, 8 Jul 2021 20:42:40 +0800
From: Shaobo Huang <huangshaobo6@...wei.com>
To: <gregkh@...uxfoundation.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux@....linux.org.uk>,
<mhiramat@...nel.org>, <tixy@...aro.org>
CC: <huangshaobo6@...wei.com>, <chenzefeng2@...wei.com>,
<kepler.chenxin@...wei.com>, <liucheng32@...wei.com>,
<nixiaoming@...wei.com>, <xiaoqian9@...wei.com>,
<young.liuyang@...wei.com>, <zengweilin@...wei.com>
Subject: ping // [PATCH 4.4.y] arm: kprobes: Allow to handle reentered kprobe on single-stepping
ping
On Sat, Feb 27, 2021 at 05:17:01PM +0800, huangshaobo wrote:
> From: Masami Hiramatsu <mhiramat@...nel.org>
>
> commit f3fbd7ec62dec1528fb8044034e2885f2b257941 upstream
>
> 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@...nel.org>
> Signed-off-by: Jon Medhurst <tixy@...aro.org>
> Fixes: 24ba613c9d6c ("ARM kprobes: core code")
> Cc: stable@...r.kernel.org #v2.6.25~v4.11
> Signed-off-by: huangshaobo <huangshaobo6@...wei.com>
> ---
> arch/arm/probes/kprobes/core.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Powered by blists - more mailing lists