From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: John 'Warthog9' Hawley <warthog9@eaglescrag.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1
Date: Tue, 28 Jun 2022 11:24:42 -0400 [thread overview]
Message-ID: <20220628112442.2b530c3b@gandalf.local.home> (raw)
In-Reply-To: <25C37F40-7D8E-41C6-961F-0774C8138CCB@oracle.com>
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
next prev parent reply other threads:[~2022-06-28 15:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 15:22 possible trace_printk() bug in v5.19-rc1 Chuck Lever III
2022-06-16 15:34 ` Steven Rostedt
2022-06-16 15:36 ` Chuck Lever III
2022-06-16 15:43 ` Steven Rostedt
2022-06-16 18:07 ` Chuck Lever III
2022-06-17 19:50 ` Steven Rostedt
2022-06-18 1:28 ` Chuck Lever III
2022-06-20 0:57 ` Chuck Lever III
2022-06-24 18:23 ` Chuck Lever III
2022-06-24 23:08 ` Steven Rostedt
2022-06-25 17:15 ` Chuck Lever III
2022-06-25 17:45 ` Steven Rostedt
2022-06-25 18:28 ` John 'Warthog9' Hawley
2022-06-26 3:01 ` John 'Warthog9' Hawley
2022-06-27 17:08 ` Chuck Lever III
2022-06-27 17:11 ` Steven Rostedt
2022-06-27 17:19 ` Chuck Lever III
2022-06-27 19:01 ` Steven Rostedt
2022-06-28 15:24 ` Steven Rostedt [this message]
2022-06-25 18:50 ` Chuck Lever III
2022-06-25 23:01 ` Steven Rostedt
2022-06-26 17:09 ` Chuck Lever III
2022-06-27 15:43 ` Steven Rostedt
2022-06-27 15:51 ` Chuck Lever III
2022-06-27 16:02 ` Steven Rostedt
2022-06-28 3:59 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220628112442.2b530c3b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog9@eaglescrag.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.