diff options
| author | Chengming Zhou <[email protected]> | 2020-07-29 02:05:53 +0800 |
|---|---|---|
| committer | Steven Rostedt (VMware) <[email protected]> | 2020-07-30 19:35:19 -0400 |
| commit | 8a224ffb3f52b0027f6b7279854c71a31c48fc97 (patch) | |
| tree | b291727ca657356e28267f27f13c58ce5f7c46a1 /scripts/gcc-plugins/cyc_complexity_plugin.c | |
| parent | 96b4833b6827a62c295b149213c68b559514c929 (diff) | |
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/[email protected]
Cc: [email protected]
Fixes: 8c4f3c3fa9681 ("ftrace: Check module functions being traced on reload")
Signed-off-by: Chengming Zhou <[email protected]>
Signed-off-by: Muchun Song <[email protected]>
Signed-off-by: Steven Rostedt (VMware) <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/cyc_complexity_plugin.c')
0 files changed, 0 insertions, 0 deletions