lkml.org 
[lkml]   [2022]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: possible trace_printk() bug in v5.19-rc1
From
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

- John 'Warthog9' Hawley

\
 
 \ /
  Last update: 2022-06-26 05:03    [W:0.147 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site