Skip to content

Commit

Permalink
kprobes: Initialize kprobes at postcore_initcall
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Masami Hiramatsu authored and Steven Rostedt (VMware) committed May 26, 2019
1 parent 539b75b commit b5f8b32
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions kernel/kprobes.c
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down Expand Up @@ -2614,5 +2615,3 @@ static int __init debugfs_kprobe_init(void)

late_initcall(debugfs_kprobe_init);
#endif /* CONFIG_DEBUG_FS */

module_init(init_kprobes);

0 comments on commit b5f8b32

Please sign in to comment.