Messages in this thread | | | From | Chuck Lever III <> | Subject | Re: possible trace_printk() bug in v5.19-rc1 | Date | Thu, 16 Jun 2022 18:07:51 +0000 |
| |
> On Jun 16, 2022, at 11:43 AM, Steven Rostedt <rostedt@goodmis.org> wrote: > > On Thu, 16 Jun 2022 15:36:43 +0000 > Chuck Lever III <chuck.lever@oracle.com> wrote: > >> I haven't explicitly removed nfsd.ko, and lsmod says it's still there. >> And, trace_printk was working as expected on v5.18. > > If you were to add a printk() with the same format in the same location, > does it work? > > That is: > > printk("%pS still here\n", __func__);
Sorry for the delay; lunch was mandatory-to-implement.
This code:
pr_info("%pS\n", (void *)_THIS_IP_);
generates:
Jun 16 14:05:53 klimt.1015granger.net kernel: nfsd_file_slab_free+0xb6/0x10a [nfsd]
-- Chuck Lever
| |