Messages in this thread | | | Date | Tue, 28 Jun 2022 11:24:42 -0400 | From | Steven Rostedt <> | Subject | Re: possible trace_printk() bug in v5.19-rc1 |
| |
On Mon, 27 Jun 2022 17:19:18 +0000 Chuck Lever III <chuck.lever@oracle.com> wrote:
> > The symbol lookup problem still exists. What about the get_sockaddr() not > > processing? > > "trace-cmd report" no longer produces the get_sockaddr warning messages, > but tracepoints that use __get_sockaddr() still FAIL TO PARSE on my > system: > > nfsd-1167 [005] 117.853235: nfsd_cb_probe: [FAILED TO PARSE] state=0x1 cl_boot=1656349219 cl_id=3054917767 addr=ARRAY[02, 00, 00, 00, c0, a8, 02, 43, 00, 00, 00, 00, 00, 00, 00, 00] > kworker/u24:2-985 [003] 117.853368: nfsd_cb_setup: [FAILED TO PARSE] cl_boot=1656349219 cl_id=3054917767 authflavor=0x1 addr=ARRAY[02, 00, 00, 00, c0, a8, 02, 43, 00, 00, 00, 00, 00, 00, 00, 00] netid=rdma > kworker/u24:2-985 [003] 117.853370: nfsd_cb_state: [FAILED TO PARSE] state=0x0 cl_boot=1656349219 cl_id=3054917767 addr=ARRAY[02, 00, 00, 00, c0, a8, 02, 43, 00, 00, 00, 00, 00, 00, 00, 00] >
I remember writing a patch to fix this, but it looks to never have been applied. And worse yet, I can't find it :-/
Oh well, I guess I just need to write it again.
-- Steve
| |