Re: [for-next][PATCH 12/16] kprobes: Initialize kprobes at postcore_initcall

From: Steven Rostedt
Date: Tue Jul 09 2019 - 11:18:38 EST


On Tue, 9 Jul 2019 21:51:24 +0900
Masami Hiramatsu <mhiramat@xxxxxxxxxx> wrote:

> > Masami,
> >
> > If you give me an Acked-by, I'll add it to my tree.
>
> Sorry for late reply, but I want to keep the test running right after
> initialization as the first user of kprobes at that timing, since
> other user can start using kprobes right after init_kprobes().
> So this issue must be fixed in moving the init_kprobes() itself
> right after arch_initcall() (and that is subsys_initcall)
>
> Catalin, Mark, could you ensure the below patch can fix your issue?
>
> https://lore.kernel.org/lkml/20190625191545.245259106@xxxxxxxxxxx/
>
> And if so, Steve, could you push above one (which seems already in your
> tree) to next as a fix?

Bah, I forgot to push. I usually do that right after I send the series.

I just pushed to my for-next branch:

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git

Can you see if that fixes the issue. If so, then we don't need to do
anything.

Thanks!

-- Steve