On Thu, 2 Aug 2018 10:02:40 +0900 Masami Hiramatsu <[email protected]> wrote:
> On Fri, 27 Jul 2018 21:15:08 +0900 > Masami Hiramatsu <[email protected]> wrote: > > > --- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc > > +++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc > > @@ -4,11 +4,18 @@ > > > > [ -f kprobe_events ] || exit_unsupported # this is configurable > > > > +rmmod trace-printk ||: > > +if ! modprobe trace-printk.ko ; then > > + echo "No trace-printk sample module - please make > > CONFIG_SAMPLE_TRACE_PRINTK= > > +m" > > + exit_unresolved; > > +fi > > + > > +MOD=trace_printk > > +FUNC=trace_printk_irq_work > > Hmm, this caused a problem with CONFIG_KPROBE_EVENTS_ON_NOTRACE=n. > However, as far as I can see, the trace_printk_irq_work() is not > marked as notrace... Ah, I found this was caused by my prevent probe on notrace patch. I was a bit too greedy to check out-of-range probes in it. I'll fix that. Thank you, -- Masami Hiramatsu <[email protected]>
