From: Steven Rostedt <rostedt@goodmis.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH] libtraceevent: Add processing of __get_sockaddr() and __get_sockaddr_rel()
Date: Fri, 9 Sep 2022 14:31:39 -0400 [thread overview]
Message-ID: <20220909143139.20a65f46@gandalf.local.home> (raw)
In-Reply-To: <0BB398D4-F990-4875-B222-47826788836B@oracle.com>
On Fri, 9 Sep 2022 18:00:45 +0000
Chuck Lever III <chuck.lever@oracle.com> wrote:
> This is a freshly-updated Fedora 36 system running v6.0-rc4,
> and the __sockaddr stuff still doesn't work.
>
> mount.nfs-1639 [002] 406.390138: svc_xprt_enqueue: [FAILED TO PARSE] server=ARRAY[02, 00, 8a, 97, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] client=<E8>sl flags=0x4c03 netns_ino=4026531840 pid=0
> mount.nfs-1639 [002] 406.390360: svcsock_new_socket: type=STREAM family=AF_INET6 (listener)
> mount.nfs-1639 [002] 406.390361: svc_xprt_enqueue: [FAILED TO PARSE] server=ARRAY[0a, 00, a7, e7, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] client=*<FC>% flags=0x4c03 netns_ino=4026531840 pid=0
> mount.nfs-1639 [002] 406.390439: rpc_task_begin: task:00000002@00000002 flags=DYNAMIC|NO_ROUND_ROBIN|SOFT|TIMEOUT|NORTO|CRED_NOREF runstate=ACTIVE status=0 action=0x0
> mount.nfs-1639 [002] 406.390440: rpc_task_run_action: task:00000002@00000002 flags=DYNAMIC|NO_ROUND_ROBIN|SOFT|TIMEOUT|NORTO|CRED_NOREF runstate=RUNNING|ACTIVE status=0 action=call_start
> mount.nfs-1639 [002] 406.390440: rpc_request: task:00000002@00000002 nfsv4 SETCLIENTID (sync)
> NFSv4 callback-1642 [006] 406.390440: svc_xprt_dequeue: [FAILED TO PARSE] server=ARRAY[02, 00, 8a, 97, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] client=<CA>d^F flags=0x4c83 netns_ino=4026531840 wakeup=0x18325fae
>
> # dnf list libtrace\*
> Last metadata expiration check: 1:27:00 ago on Fri 09 Sep 2022 12:31:57 PM EDT.
> Installed Packages
> libtracecmd.x86_64 1.1.3-2.fc36 @updates
> libtraceevent.x86_64 1.5.3-2.fc36 @updates
> libtracefs.x86_64 1.3.1-2.fc36 @updates
> Available Packages
> libtracecmd.i686 1.1.0-3.fc36 fedora
> libtracecmd-devel.i686 1.1.0-3.fc36 fedora
> libtracecmd-devel.x86_64 1.1.3-2.fc36 updates
> libtraceevent.i686 1.5.3-2.fc36 updates
> libtraceevent-devel.i686 1.5.3-2.fc36 updates
> libtraceevent-devel.x86_64 1.5.3-2.fc36 updates
That parsing was added in libtraceevent 1.6.2.
-- Steve
> libtracefs.i686 1.3.1-2.fc36 updates
> libtracefs-devel.i686 1.3.1-2.fc36 updates
> libtracefs-devel.x86_64 1.3.1-2.fc36 updates
prev parent reply other threads:[~2022-09-09 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 16:23 [PATCH] libtraceevent: Add processing of __get_sockaddr() and __get_sockaddr_rel() Steven Rostedt
2022-09-09 18:00 ` Chuck Lever III
2022-09-09 18:31 ` Steven Rostedt [this message]
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=20220909143139.20a65f46@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chuck.lever@oracle.com \
--cc=linux-trace-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).