All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: ChunyouTang <tangchunyou@163.com>
Cc: tangchunyou@yulong.com, Masami Hiramatsu <mhiramat@kernel.org>,
	stable@vger.kernel.org,
	"Naveen N . Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: [PATCH] tracing/kprobes: Do the notrace functions check without kprobes on ftrace
Date: Wed, 13 Jan 2021 22:13:07 -0500	[thread overview]
Message-ID: <20210113221307.5456f7fc@oasis.local.home> (raw)
In-Reply-To: <20210114023627.1555-1-tangchunyou@163.com>

On Thu, 14 Jan 2021 10:36:27 +0800
ChunyouTang <tangchunyou@163.com> wrote:

> From: Masami Hiramatsu <mhiramat@kernel.org>
> 
> Enable the notrace function check on the architecture which doesn't
> support kprobes on ftrace but support dynamic ftrace. This notrace
> function check is not only for the kprobes on ftrace but also
> sw-breakpoint based kprobes.
> Thus there is no reason to limit this check for the arch which
> supports kprobes on ftrace.
> 
> This also changes the dependency of Kconfig. Because kprobe event
> uses the function tracer's address list for identifying notrace
> function, if the CONFIG_DYNAMIC_FTRACE=n, it can not check whether
> the target function is notrace or not.
> 

Please be careful to how you send internal patches, and not
automatically Cc everyone in the Cc list of the patch.

-- Steve


> Link: https://lkml.kernel.org/r/20210105065730.2634785-1-naveen.n.rao@linux.vnet.ibm.com
> Link: https://lkml.kernel.org/r/161007957862.114704.4512260007555399463.stgit@devnote2
> 
> Cc: stable@vger.kernel.org
> Fixes: 45408c4f92506 ("tracing: kprobes: Prohibit probing on notrace function")
> Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
>  kernel/trace/Kconfig        | 2 +-
>  kernel/trace/trace_kprobe.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index d5a19413d4f8..c1a62ae7e812 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -538,7 +538,7 @@ config KPROBE_EVENTS
>  config KPROBE_EVENTS_ON_NOTRACE
>  	bool "Do NOT protect notrace function from kprobe events"
>  	depends on KPROBE_EVENTS
> -	depends on KPROBES_ON_FTRACE
> +	depends on DYNAMIC_FTRACE
>  	default n
>  	help
>  	  This is only for the developers who want to debug ftrace itself
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index 9c31f42245e9..e6fba1798771 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -434,7 +434,7 @@ static int disable_trace_kprobe(struct trace_event_call *call,
>  	return 0;
>  }
>  
> -#if defined(CONFIG_KPROBES_ON_FTRACE) && \
> +#if defined(CONFIG_DYNAMIC_FTRACE) && \
>  	!defined(CONFIG_KPROBE_EVENTS_ON_NOTRACE)
>  static bool __within_notrace_func(unsigned long addr)
>  {


  reply	other threads:[~2021-01-14  3:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  2:36 [PATCH] tracing/kprobes: Do the notrace functions check without kprobes on ftrace ChunyouTang
2021-01-14  3:13 ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-14  2:51 ChunyouTang
2021-01-06  3:20 Masami Hiramatsu
2021-01-06 14:56 ` Steven Rostedt
2021-01-07 14:13 ` Steven Rostedt
2021-01-08  4:19   ` Masami Hiramatsu

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=20210113221307.5456f7fc@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=mhiramat@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=tangchunyou@163.com \
    --cc=tangchunyou@yulong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.