[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4172710c-58ad-a674-b892-868a13c4a149@linux.alibaba.com>
Date: Tue, 7 Dec 2021 09:29:27 +0800
From: Yinan Liu <yinan@...ux.alibaba.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: peterz@...radead.org, mark-pk.tsai@...iatek.com, mingo@...hat.com,
linux-kernel@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH v6 1/2] scripts: ftrace - move the sort-processing in
ftrace_init
>> After applying this, I get a failure on the kprobe self tests at boot up:
>>
>> Testing ftrace filter: OK
>> trace_kprobe: Testing kprobe tracing:
>> trace_kprobe: Could not probe notrace function kprobe_trace_selftest_target
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 1 at kernel/trace/trace_kprobe.c:1973 kprobe_trace_self_tests_init+0x5c/0x497
>> Modules linked in:
>
> And I added the below patch, and it shows that the section is not properly
> sorted. Something went wrong with your sorting.
>
> I plan on keeping this check, at least as a compile option, to make sure
> that the output is sorted, otherwise things will silently fail if they are
> not.
>
> This patch produced:
>
> [ 1.315419] ftrace: allocating 43510 entries in 170 pages
> [ 1.320638] ------------[ cut here ]------------
> [ 1.325227] [3] x86_pnpbios_disabled+0x0/0x1c at 8a51c707 is not sorted with __traceiter_initcall_level+0x0/0x60 at 87000660
>
> I'm dropping the patches until this is "sorted out" :-)
>
> -- Steve
>
Hi, steven
Sorry, I just saw the email yesterday. Recently my computer is not
around. I'm not sure what went wrong at the moment. I will fix it.
Best regards!
-- Yinan Liu
Powered by blists - more mailing lists