diff options
author | Masami Hiramatsu <mhiramat@kernel.org> | 2018-08-02 09:50:48 +0200 |
---|---|---|
committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-08-02 18:34:41 +0200 |
commit | 6bc6c77cfc6747292d5865d124cc31333b1b8536 (patch) | |
tree | d1099447d280fb8fa96019fc6dab2d23e904f424 /scripts | |
parent | ftrace: Use true and false for boolean values in ops_references_rec() (diff) | |
download | linux-6bc6c77cfc6747292d5865d124cc31333b1b8536.tar.xz linux-6bc6c77cfc6747292d5865d124cc31333b1b8536.zip |
tracing/kprobes: Fix within_notrace_func() to check only notrace functions
Fix within_notrace_func() to check only notrace functions and to ignore the
kprobe-event which can not solve symbol addresses.
within_notrace_func() returns true if the given kprobe events probe point
seems to be out-of-range. But that is not the correct place to check for it,
it should be done in kprobes afterwards.
kprobe-events allow users to define a probe point on "currently unloaded
module" so that it can trace the event during module load. In this case, the
user will put a probe on a symbol which is not in kallsyms yet and it hits
the within_notrace_func(). As a result, kprobe-events always refuses if
user defines a probe on a "currenly unloaded module".
Fixes: commit 45408c4f9250 ("tracing: kprobes: Prohibit probing on notrace function")
Link: http://lkml.kernel.org/r/153319624799.29007.13604430345640129926.stgit@devbox
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions