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, 20 Jun 2022 00:57:23 +0000
From:   Chuck Lever III <chuck.lever@...cle.com>
To:     Steven Rostedt <rostedt@...dmis.org>
CC:     LKML <linux-kernel@...r.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1

Hi Steve-

> On Jun 17, 2022, at 9:28 PM, Chuck Lever III <chuck.lever@...cle.com> wrote:
> 
> 
> 
>> On Jun 17, 2022, at 3:50 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
>> 
>> On Thu, 16 Jun 2022 15:36:43 +0000
>> Chuck Lever III <chuck.lever@...cle.com> wrote:
>> 
>>>> Did you remove any modules before displaying the trace? 
>>> 
>>> I haven't explicitly removed nfsd.ko, and lsmod says it's still there.
>>> And, trace_printk was working as expected on v5.18.
>> 
>> Are you sure?
> 
> Yes, I'm sure. I just checked out v5.18 and built it with the
> same CONFIG. trace_printk() on that kernel generates function
> names as expected.

I moved my development work to another system, and bisected. The
result:

91fb02f31505 ("module: Move kallsyms support into a separate file")


--
Chuck Lever