kprobes: Initialize kprobes at postcore_initcall

Initialize kprobes at postcore_initcall level instead of module_init
since kprobes is not a module, and it depends on only subsystems
initialized in core_initcall.
This will allow ftrace kprobe event to add new events when it is
initializing because ftrace kprobe event is initialized at
later initcall level.

Link: http://lkml.kernel.org/r/155851394736.15728.13626739508905120098.stgit@devnote2

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
This commit is contained in:
Masami Hiramatsu 2019-05-22 17:32:27 +09:00 committed by Steven Rostedt (VMware)
parent 539b75b2b9
commit b5f8b32c93
1 changed files with 1 additions and 2 deletions

View File

@ -2289,6 +2289,7 @@ static int __init init_kprobes(void)
init_test_probes();
return err;
}
postcore_initcall(init_kprobes);
#ifdef CONFIG_DEBUG_FS
static void report_probe(struct seq_file *pi, struct kprobe *p,
@ -2614,5 +2615,3 @@ error:
late_initcall(debugfs_kprobe_init);
#endif /* CONFIG_DEBUG_FS */
module_init(init_kprobes);