Messages in this thread | | | Date | Mon, 27 Jun 2022 23:59:57 -0400 | From | Steven Rostedt <> | Subject | Re: possible trace_printk() bug in v5.19-rc1 |
| |
On Fri, 24 Jun 2022 19:08:19 -0400 Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 20 Jun 2022 00:57:23 +0000 > Chuck Lever III <chuck.lever@oracle.com> wrote: > > > > Yes, I'm sure. I just checked out v5.18 and built it with the > > > same CONFIG. trace_printk() on that kernel generates function > > > names as expected. > > > > I moved my development work to another system, and bisected. The > > result: > > > > 91fb02f31505 ("module: Move kallsyms support into a separate file") > > Hmm, right below that it says: > > "No functional change." > > I'm guessing it may not be as reliably reproducible.
I take this back. I bisected it down to this commit as well.
I found another patch in that series that has a function change, so I do not trust this. This most definitely has a functional change, as the output of kallsyms changes with it. I'll report it against that patch submission.
-- Steve
> > And is this an issue with trace-cmd output or reading the trace file?
| |