diff options
author | 2020-07-29 02:05:54 +0800 | |
---|---|---|
committer | 2020-07-30 22:45:31 -0400 | |
commit | c5f51572a7fdff5be9e67c231de593155f394ab3 (patch) | |
tree | dda7c7bcb4e8c08e54f9d9864e31116c843f5676 /kernel/trace/trace.c | |
parent | ftrace: Setup correct FTRACE_FL_REGS flags for module (diff) | |
download | linux-dev-c5f51572a7fdff5be9e67c231de593155f394ab3.tar.xz linux-dev-c5f51572a7fdff5be9e67c231de593155f394ab3.zip |
ftrace: Do not let direct or IPMODIFY ftrace_ops be added to module and set trampolines
When inserting a module, we find all ftrace_ops referencing it on the
ftrace_ops_list. But FTRACE_OPS_FL_DIRECT and FTRACE_OPS_FL_IPMODIFY
flags are special, and should not be set automatically. So warn and
skip ftrace_ops that have these two flags set and adding new code.
Also check if only one ftrace_ops references the module, in which case
we can use a trampoline as an optimization.
Link: https://lkml.kernel.org/r/20200728180554.65203-2-zhouchengming@bytedance.com
Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace.c')
0 files changed, 0 insertions, 0 deletions