Re: possible trace_printk() bug in v5.19-rc1

[Steven Rostedt]

On Mon, 27 Jun 2022 17:08:03 +0000
Chuck Lever III <chuck.lever@xxxxxxxxxx> wrote:

> Updated from your copr repo. The problem persists.

The symbol lookup problem still exists. What about the get_sockaddr() not
processing?

Would you be able to send me a trace.dat file that has this issue?

Thanks,

-- Steve

> 
> [root@manet ~]# trace-cmd version
> 
> trace-cmd version 3.1.1 (not-a-git-repo)
> 
> usage:
>   trace-cmd [COMMAND] ...
> 
>   commands:
>      record - record a trace into a trace.dat file
>      set - set a ftrace configuration parameter
> 
>   ...
> 
>      dump - read out the meta data from a trace file
>      convert - convert trace file to different version
> 
> [root@manet ~]# ls -l /usr/lib64/libtrace*
> lrwxrwxrwx 1 root root     20 Jul 22  2021 /usr/lib64/libtracecmd.so.1 -> libtracecmd.so.1.0.0
> -rwxr-xr-x 1 root root 142032 Jul 22  2021 /usr/lib64/libtracecmd.so.1.0.0
> lrwxrwxrwx 1 root root     22 Jun 25 14:28 /usr/lib64/libtraceevent.so.1 -> libtraceevent.so.1.6.1
> -rwxr-xr-x 1 root root 153944 Jun 25 14:29 /usr/lib64/libtraceevent.so.1.6.1
> lrwxrwxrwx 1 root root     19 Jun 25 17:53 /usr/lib64/libtracefs.so.1 -> libtracefs.so.1.4.1
> -rwxr-xr-x 1 root root 133384 Jun 25 17:53 /usr/lib64/libtracefs.so.1.4.1
> [root@manet ~]#