mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-28 02:32:09 -04:00
ftrace: Ignore FTRACE_FL_DISABLED while walking dyn_ftrace records
ftrace_shutdown() checks for sanity of ftrace records
and if dyn_ftrace->flags is not zero, it will warn.
It can happen that 'flags' are set to FTRACE_FL_DISABLED at this point,
since some module was loaded, but before ftrace_module_enable()
cleared the flags for this module.
In other words the module.c is doing:
ftrace_module_init(mod); // calls ftrace_update_code() that sets flags=FTRACE_FL_DISABLED
... // here ftrace_shutdown() is called that warns, since
err = prepare_coming_module(mod); // didn't have a chance to clear FTRACE_FL_DISABLED
Fix it by ignoring disabled records.
It's similar to what __ftrace_hash_rec_update() is already doing.
Link: http://lkml.kernel.org/r/[email protected]
Cc: [email protected]
Fixes: b7ffffbb46 "ftrace: Add infrastructure for delayed enabling of module functions"
Signed-off-by: Alexei Starovoitov <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
This commit is contained in:
parent
a25f0944ba
commit
977c1f9c8c
1 changed files with 1 additions and 1 deletions
|
|
@ -2763,7 +2763,7 @@ static int ftrace_shutdown(struct ftrace_ops *ops, int command)
|
|||
struct dyn_ftrace *rec;
|
||||
|
||||
do_for_each_ftrace_rec(pg, rec) {
|
||||
if (FTRACE_WARN_ON_ONCE(rec->flags))
|
||||
if (FTRACE_WARN_ON_ONCE(rec->flags & ~FTRACE_FL_DISABLED))
|
||||
pr_warn(" %pS flags:%lx\n",
|
||||
(void *)rec->ip, rec->flags);
|
||||
} while_for_each_ftrace_rec();
|
||||
|
|
|
|||
Loading…
Reference in a new issue