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: <20220627114340.4d89842b@gandalf.local.home>
Date:   Mon, 27 Jun 2022 11:43:40 -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 Sun, 26 Jun 2022 17:09:31 +0000
Chuck Lever III <chuck.lever@...cle.com> wrote:

> [cel@...et lib]$ cd /usr/lib64/
> [cel@...et lib64]$ ls libtrace*
> libtracecmd.so.1  libtracecmd.so.1.0.0  libtraceevent.so.1  libtraceevent.so.1.2.1  libtracefs.so.1  libtracefs.so.1.1.1
> [cel@...et lib64]$

According to https://trace-cmd.org

The latest libraries are:

 libtraceevent 1.6.1
 libtracefs 1.4.1

I'm guessing you may have a buggy version.

-- Steve