From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [ftrace/kprobes PATCH 0/3] tracing: probeevent: Fix module symbol probing
Date: Thu, 27 Sep 2018 19:48:58 +0900 [thread overview]
Message-ID: <20180927194858.7419c4ee4821f3985d3b0918@kernel.org> (raw)
In-Reply-To: <153547303754.26502.5265242979168613920.stgit@devbox>
Hello Steve,
Could you also include this series to the branch?
Thank you,
On Wed, 29 Aug 2018 01:17:18 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Hi,
>
> This series is for fixing some bugs in Steve's ftrace/kprobes branch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
>
> Which is based on my fetcharg improvement series.
>
> https://lkml.org/lkml/2018/4/25/601
>
> This includes following fixes.
>
> - Fix copy_from_user() misusing which Dan was reported.
> - Fix to reject incorrect probeevent on loaded kernel module.
> - Fix to update symbol-based argument on module.
> This also checks the symbol-based argument is correct or not when
> target module is loaded. If it is not correct, the event is kept
> unavailable.
>
> Thank you,
>
> ---
>
> Masami Hiramatsu (3):
> tracing/uprobes: Fix to return -EFAULT if copy_from_user failed
> tracing/kprobes: Check the probe on unloaded module correctly
> tracing/kprobes: Allow kprobe-events to record module symbol
>
>
> kernel/trace/trace_kprobe.c | 51 ++++++++++++++++++++++++++---------
> kernel/trace/trace_probe.c | 62 +++++++++++++++++++++++++++++++++++++------
> kernel/trace/trace_probe.h | 4 ++-
> kernel/trace/trace_uprobe.c | 2 +
> 4 files changed, 95 insertions(+), 24 deletions(-)
>
> --
> Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2018-09-27 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 16:17 [ftrace/kprobes PATCH 0/3] tracing: probeevent: Fix module symbol probing Masami Hiramatsu
2018-08-28 16:17 ` [ftrace/kprobes PATCH 1/3] tracing/uprobes: Fix to return -EFAULT if copy_from_user failed Masami Hiramatsu
2018-08-28 16:18 ` [ftrace/kprobes PATCH 2/3] tracing/kprobes: Check the probe on unloaded module correctly Masami Hiramatsu
2018-08-28 16:18 ` [ftrace/kprobes PATCH 3/3] tracing/kprobes: Allow kprobe-events to record module symbol Masami Hiramatsu
2018-10-03 19:12 ` Steven Rostedt
2018-10-04 1:11 ` Steven Rostedt
2018-10-05 8:53 ` Masami Hiramatsu
2018-09-27 10:48 ` Masami Hiramatsu [this message]
2018-10-01 15:48 ` [ftrace/kprobes PATCH 0/3] tracing: probeevent: Fix module symbol probing Steven Rostedt
2018-10-03 2:47 ` Steven Rostedt
2018-10-03 13:26 ` 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=20180927194858.7419c4ee4821f3985d3b0918@kernel.org \
--to=mhiramat@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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