From: Greg KH <gregkh@linuxfoundation.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: ShaoBo Huang <huangshaobo6@huawei.com>,
linux@armlinux.org.uk, tixy@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, young.liuyang@huawei.com,
zengweilin@huawei.com, nixiaoming@huawei.com,
chenzefeng2@huawei.com, liucheng32@huawei.com,
kepler.chenxin@huawei.com, xiaoqian9@huawei.com
Subject: Re: [PATCH 4.9.y] arm: kprobes: Allow to handle reentered kprobe on single-stepping
Date: Thu, 4 Mar 2021 14:28:37 +0100 [thread overview]
Message-ID: <YEDghZHAgdotrax3@kroah.com> (raw)
In-Reply-To: <20210303211827.eeb89c8a9b140152fbcd997c@kernel.org>
On Wed, Mar 03, 2021 at 09:18:27PM +0900, Masami Hiramatsu wrote:
> Hi ShaoBo,
>
> Thanks for backporting and real bug report!
>
> On Wed, 3 Mar 2021 15:10:52 +0800
> ShaoBo Huang <huangshaobo6@huawei.com> wrote:
>
> > From: Masami Hiramatsu <mhiramat@kernel.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@kernel.org>
> > Signed-off-by: Jon Medhurst <tixy@linaro.org>
> > Fixes: 24ba613c9d6c ("ARM kprobes: core code")
> > Cc: stable@vger.kernel.org #v2.6.25~v4.11
> > Signed-off-by: huangshaobo <huangshaobo6@huawei.com>
> > ---
> > arch/arm/probes/kprobes/core.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/arch/arm/probes/kprobes/core.c b/arch/arm/probes/kprobes/core.c
> > index 3eb018fa1a1f..c3362ddd6c4c 100644
> > --- a/arch/arm/probes/kprobes/core.c
> > +++ b/arch/arm/probes/kprobes/core.c
> > @@ -270,6 +270,7 @@ void __kprobes kprobe_handler(struct pt_regs *regs)
> > switch (kcb->kprobe_status) {
> > case KPROBE_HIT_ACTIVE:
> > case KPROBE_HIT_SSDONE:
> > + case KPROBE_HIT_SS:
> > /* A pre- or post-handler probe got us here. */
> > kprobes_inc_nmissed_count(p);
> > save_previous_kprobe(kcb);
> > @@ -278,6 +279,11 @@ void __kprobes kprobe_handler(struct pt_regs *regs)
> > singlestep(p, regs, kcb);
> > restore_previous_kprobe(kcb);
> > break;
> > + case KPROBE_REENTER:
> > + /* A nested probe was hit in FIQ, it is a BUG */
> > + pr_warn("Unrecoverable kprobe detected at %p.\n",
> > + p->addr);
> > + /* fall through */
> > default:
> > /* impossible cases */
> > BUG();
> > --
> > 2.12.3
> >
Also queued up to 4.4.y as well.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-04 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 7:10 [PATCH 4.9.y] arm: kprobes: Allow to handle reentered kprobe on single-stepping ShaoBo Huang
2021-03-03 12:18 ` Masami Hiramatsu
2021-03-04 13:28 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEDghZHAgdotrax3@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chenzefeng2@huawei.com \
--cc=huangshaobo6@huawei.com \
--cc=kepler.chenxin@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liucheng32@huawei.com \
--cc=mhiramat@kernel.org \
--cc=nixiaoming@huawei.com \
--cc=tixy@linaro.org \
--cc=xiaoqian9@huawei.com \
--cc=young.liuyang@huawei.com \
--cc=zengweilin@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).