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

[Chuck Lever III]

Hi Steve-

> On Jun 17, 2022, at 9:28 PM, Chuck Lever III <chuck.lever@xxxxxxxxxx> wrote:
> 
> 
> 
>> On Jun 17, 2022, at 3:50 PM, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
>> 
>> On Thu, 16 Jun 2022 15:36:43 +0000
>> Chuck Lever III <chuck.lever@xxxxxxxxxx> 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