From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH 5/5] powerpc/jprobes: Validate break handler invocation as being due to a jprobe_return()
Date: Wed, 13 Sep 2017 17:38:29 -0700 [thread overview]
Message-ID: <20170913173829.8845e0ada53fbd5338fa196f@kernel.org> (raw)
In-Reply-To: <58db21d55022d7fb95468f3b8fd3dbffec36a113.1505336870.git.naveen.n.rao@linux.vnet.ibm.com>
On Thu, 14 Sep 2017 02:50:36 +0530
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> Fix a circa 2005 FIXME by implementing a check to ensure that we
> actually got into the jprobe break handler() due to the trap in
> jprobe_return().
>
Looks good to me.
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks!
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
> ---
> This is v2 of the patch posted previously (*) to change the WARN() to a
> pr_debug() as suggested by Masami.
> (*) https://patchwork.ozlabs.org/patch/762670/
>
> - Naveen
>
> arch/powerpc/kernel/kprobes.c | 20 +++++++++-----------
> 1 file changed, 9 insertions(+), 11 deletions(-)
>
> diff --git a/arch/powerpc/kernel/kprobes.c b/arch/powerpc/kernel/kprobes.c
> index db40b13fd3d1..5b26d5202273 100644
> --- a/arch/powerpc/kernel/kprobes.c
> +++ b/arch/powerpc/kernel/kprobes.c
> @@ -648,24 +648,22 @@ NOKPROBE_SYMBOL(setjmp_pre_handler);
>
> void __used jprobe_return(void)
> {
> - asm volatile("trap" ::: "memory");
> + asm volatile("jprobe_return_trap:\n"
> + "trap\n"
> + ::: "memory");
> }
> NOKPROBE_SYMBOL(jprobe_return);
>
> -static void __used jprobe_return_end(void)
> -{
> -}
> -NOKPROBE_SYMBOL(jprobe_return_end);
> -
> int longjmp_break_handler(struct kprobe *p, struct pt_regs *regs)
> {
> struct kprobe_ctlblk *kcb = get_kprobe_ctlblk();
>
> - /*
> - * FIXME - we should ideally be validating that we got here 'cos
> - * of the "trap" in jprobe_return() above, before restoring the
> - * saved regs...
> - */
> + if (regs->nip != ppc_kallsyms_lookup_name("jprobe_return_trap")) {
> + pr_debug("longjmp_break_handler NIP (0x%lx) does not match jprobe_return_trap (0x%lx)\n",
> + regs->nip, ppc_kallsyms_lookup_name("jprobe_return_trap"));
> + return 0;
> + }
> +
> memcpy(regs, &kcb->jprobe_saved_regs, sizeof(struct pt_regs));
> /* It's OK to start function graph tracing again */
> unpause_graph_tracing();
> --
> 2.14.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-09-14 0:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 21:20 [PATCH 1/5] powerpc/kprobes: Some cosmetic updates to try_to_emulate() Naveen N. Rao
2017-09-13 21:20 ` [PATCH 2/5] powerpc/kprobes: Do not suppress instruction emulation if a single run failed Naveen N. Rao
2017-09-13 23:53 ` Masami Hiramatsu
2017-09-14 6:38 ` Naveen N. Rao
2017-09-14 9:45 ` Masami Hiramatsu
2017-09-14 10:03 ` Naveen N. Rao
2017-09-13 21:20 ` [PATCH 3/5] powerpc/kprobes: Fix warnings from __this_cpu_read() on preempt kernels Naveen N. Rao
2017-09-14 0:36 ` Masami Hiramatsu
2017-09-14 6:47 ` Naveen N. Rao
2017-09-14 10:10 ` Masami Hiramatsu
2017-09-16 11:25 ` Naveen N. Rao
2017-09-14 9:48 ` Kamalesh Babulal
2017-09-13 21:20 ` [PATCH 4/5] powerpc/jprobes: Disable preemption when triggered through ftrace Naveen N. Rao
2017-09-14 0:05 ` Masami Hiramatsu
2017-09-14 10:25 ` Naveen N. Rao
2017-09-14 10:53 ` Masami Hiramatsu
2017-09-13 21:20 ` [PATCH 5/5] powerpc/jprobes: Validate break handler invocation as being due to a jprobe_return() Naveen N. Rao
2017-09-14 0:38 ` Masami Hiramatsu [this message]
2017-09-13 23:18 ` [PATCH 1/5] powerpc/kprobes: Some cosmetic updates to try_to_emulate() Masami Hiramatsu
2017-09-14 6:16 ` Kamalesh Babulal
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=20170913173829.8845e0ada53fbd5338fa196f@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.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).