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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20220625134552.08c1a23a@rorschach.local.home>
Date:   Sat, 25 Jun 2022 13:45:52 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Chuck Lever III <chuck.lever@...cle.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        John 'Warthog9' Hawley <warthog9@...nel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1

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? ;-)

-- Steve


> 
> usage:
>   trace-cmd [COMMAND] ...
> 
>   commands:
>      record - record a trace into a trace.dat file
>      set - set a ftrace configuration parameter
> 
>  ...
> 
>      check-events - parse trace event formats
>      dump - read out the meta data from a trace file
> 
> [root@...et ~]#