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]

Date:   Mon, 27 Jun 2022 12:02:06 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Chuck Lever III <chuck.lever@...cle.com>
Cc:     John 'Warthog9' Hawley <warthog9@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1

On Mon, 27 Jun 2022 15:51:04 +0000
Chuck Lever III <chuck.lever@...cle.com> wrote:

> I'd like to avoid having to maintain the latest version of
> the tool and its libraries by hand on all of my development
> systems.

But can you just verify that the new ones fix the issue in one of your
builds?

I'm not a fedora maintainer, so I have no control over what they ship. But
if you can prove that the issues you have are resolved when upgrading, then
there's nothing more I can do. It's up to fedora to update the libraries.

If it's still broken in the latest versions, then I can do something. But
without verification, this is just a fedora bug, not an upstream one.

-- Steve