lkml.org 
[lkml]   [2022]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: possible trace_printk() bug in v5.19-rc1
    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.

    And is this an issue with trace-cmd output or reading the trace file?

    -- Steve

    \
     
     \ /
      Last update: 2022-06-25 01:09    [W:3.454 / U:0.312 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site