mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Francis Deslauriers <francis.deslauriers@efficios.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	shuah@kernel.org,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] tracing: kprobes: Prohibit probing on notrace functions
Date: Tue, 31 Jul 2018 08:00:59 +0900	[thread overview]
Message-ID: <20180731080059.be34e021d6758925c70dbc6b@kernel.org> (raw)
In-Reply-To: <CADcCL0hWtn=r-AjpKgB_JKeL1aTbeZPpoKeVXH8Z_FnJYyaTbA@mail.gmail.com>

On Mon, 30 Jul 2018 12:06:17 -0400
Francis Deslauriers <francis.deslauriers@efficios.com> wrote:

> Hi Masami,
> I just tested the patch-set and it still prevents the crash I was witnessing.
> You can add my tested-by.
> Tested-by: Francis Deslauriers <francis.deslauriers@efficios.com>

Thanks Francis!


> 
> Thank you for pushing this forward!
> Francis
> Le lun. 30 juill. 2018, à 06 h 20, Masami Hiramatsu
> <mhiramat@kernel.org> a écrit :
> >
> > Hi,
> >
> > This is the 5th version of the series to prohibit kprobe
> > on notrace functions.
> >
> > This fixes a build error when CONFIG_FUNCTION_TRACER=y but
> > DYNAMIC_FTRACE=n. Finally I decided to recover the approach
> > in the 1st version, made it depends on CONFIG_KPROBES_ON_FTRACE=y.
> > It is the simplest and enough to prohibiting kernel crash.
> >
> > So, in summary, if CONFIG_KPROBES_ON_FTRACE=y (which depends
> > on CONFIG_DYNAMIC_FTRACE=y, so ftrace_location_range must be
> > there) && CONFIG_KPROBE_EVENTS_ON_NOTRACE=n (default),
> > kprobe events can not be defined on notrace function.
> > Otherwides (means CONFIG_KPROBES_ON_FTRACE=n or
> > CONFIG_KPROBE_EVENTS_ON_NOTRACE=y), we can put kprobe events
> > on notrace functions.
> >
> > Francis, I dropped your tested-by because I got many kbuild
> > errors and fixed it. If you can, could you test it again?
> >
> > Thank you,
> >
> > ---
> >
> > Francis Deslauriers (1):
> >       selftest/ftrace: Move kprobe selftest function to separate compile unit
> >
> > Masami Hiramatsu (2):
> >       tracing: kprobes: Prohibit probing on notrace function
> >       selftests/ftrace: Fix kprobe string testcase to not probe notrace function
> >
> >
> >  kernel/trace/Kconfig                               |   20 +++++++
> >  kernel/trace/Makefile                              |    5 ++
> >  kernel/trace/trace_kprobe.c                        |   59 +++++++++++++-------
> >  kernel/trace/trace_kprobe_selftest.c               |   10 +++
> >  kernel/trace/trace_kprobe_selftest.h               |    7 ++
> >  .../ftrace/test.d/kprobe/kprobe_args_string.tc     |   30 ++++------
> >  .../selftests/ftrace/test.d/kprobe/probepoint.tc   |    2 -
> >  7 files changed, 94 insertions(+), 39 deletions(-)
> >  create mode 100644 kernel/trace/trace_kprobe_selftest.c
> >  create mode 100644 kernel/trace/trace_kprobe_selftest.h
> >
> > --
> > Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
> 
> 
> 
> --
> Francis Deslauriers
> Software developer
> EfficiOS inc.


-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2018-07-30 23:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 10:19 Masami Hiramatsu
2018-07-30 10:20 ` [PATCH v5 1/3] tracing: kprobes: Prohibit probing on notrace function Masami Hiramatsu
2018-07-30 22:40   ` Steven Rostedt
2018-07-31  1:04     ` Masami Hiramatsu
2018-07-30 10:20 ` [PATCH v5 2/3] selftest/ftrace: Move kprobe selftest function to separate compile unit Masami Hiramatsu
2018-07-30 10:21 ` [PATCH v5 3/3] selftests/ftrace: Fix kprobe string testcase to not probe notrace function Masami Hiramatsu
2018-07-30 16:06 ` [PATCH v5 0/3] tracing: kprobes: Prohibit probing on notrace functions Francis Deslauriers
2018-07-30 23:00   ` Masami Hiramatsu [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=20180731080059.be34e021d6758925c70dbc6b@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=francis.deslauriers@efficios.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    /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

Powered by JetHome