ftrace: Setup correct FTRACE_FL_REGS flags for module
authorChengming Zhou <zhouchengming@bytedance.com>
Tue, 28 Jul 2020 18:05:53 +0000 (02:05 +0800)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Thu, 30 Jul 2020 23:35:19 +0000 (19:35 -0400)
commit8a224ffb3f52b0027f6b7279854c71a31c48fc97
treeb291727ca657356e28267f27f13c58ce5f7c46a1
parent96b4833b6827a62c295b149213c68b559514c929
ftrace: Setup correct FTRACE_FL_REGS flags for module

When module loaded and enabled, we will use __ftrace_replace_code
for module if any ftrace_ops referenced it found. But we will get
wrong ftrace_addr for module rec in ftrace_get_addr_new, because
rec->flags has not been setup correctly. It can cause the callback
function of a ftrace_ops has FTRACE_OPS_FL_SAVE_REGS to be called
with pt_regs set to NULL.
So setup correct FTRACE_FL_REGS flags for rec when we call
referenced_filters to find ftrace_ops references it.

Link: https://lkml.kernel.org/r/20200728180554.65203-1-zhouchengming@bytedance.com
Cc: stable@vger.kernel.org
Fixes: 8c4f3c3fa9681 ("ftrace: Check module functions being traced on reload")
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>
kernel/trace/ftrace.c