From: Chuck Lever III <chuck.lever@oracle.com>
To: John 'Warthog9' Hawley <warthog9@eaglescrag.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1
Date: Mon, 27 Jun 2022 17:08:03 +0000 [thread overview]
Message-ID: <308F6A3B-1FB9-42CD-8239-12B0FD0F5FDB@oracle.com> (raw)
In-Reply-To: <12417afa-331b-e0f6-a3b0-19623e38590b@eaglescrag.net>
> On Jun 25, 2022, at 11:01 PM, John 'Warthog9' Hawley <warthog9@eaglescrag.net> wrote:
>
> On 6/25/22 11:28, John 'Warthog9' Hawley wrote:
>> On 6/25/2022 10:45 AM, Steven Rostedt wrote:
>>> On Sat, 25 Jun 2022 17:15:07 +0000
>>> Chuck Lever III <chuck.lever@oracle.com> wrote:
>>>
>>>> [root@manet ~]# cat /etc/redhat-release
>>>> Fedora release 35 (Thirty Five)
>>>> [root@manet ~]# trace-cmd version
>>>>
>>>> trace-cmd version 2.9.2 (not-a-git-repo)
>>>
>>> Ug, that's very old. Fedora should be shipping 3.1.1 soon.
>>>
>>> Right John? ;-)
>> I've got 3.0.2 in there right now (~3mo old) and I've started the builds on the latest tags (REALLY need to automate this!), probably have latest tags built/packaged by tonight.
>> https://copr.fedorainfracloud.org/coprs/warthog9/tracing/
>
> As, vaguely, promised this morning trace-cmd, and all libraries needed for everything but centos-9-stream x86_64 (it's having some fit about not finding trace_seq_vprintf and trace_seq_printf, which is weird that it finds it on every other build...)
>
> https://copr.fedorainfracloud.org/coprs/warthog9/tracing/build/4564577/
>
> so dnf copr enable warthog9/tracing and dnf update should snag 3.1.1
Updated from your copr repo. The problem persists.
[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 ~]#
--
Chuck Lever
next prev parent reply other threads:[~2022-06-27 17:08 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 [this message]
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
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=308F6A3B-1FB9-42CD-8239-12B0FD0F5FDB@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.