linux-kernel - Re: possible trace_printk() bug in v5.19-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 27 Jun 2022 17:08:03 +0000
From:   Chuck Lever III <chuck.lever@...cle.com>
To:     John 'Warthog9' Hawley <warthog9@...lescrag.net>
CC:     Steven Rostedt <rostedt@...dmis.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1



> On Jun 25, 2022, at 11:01 PM, John 'Warthog9' Hawley <warthog9@...lescrag.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@...cle.com> wrote:
>>> 
>>>> [root@...et ~]# cat /etc/redhat-release
>>>> Fedora release 35 (Thirty Five)
>>>> [root@...et ~]# 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@...et ~]# 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@...et ~]# 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@...et ~]#


--
Chuck Lever