From: Chuck Lever III <chuck.lever@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible trace_printk() bug in v5.19-rc1
Date: Thu, 16 Jun 2022 18:07:51 +0000 [thread overview]
Message-ID: <88ADA44D-E457-4DA4-BD65-73F583217363@oracle.com> (raw)
In-Reply-To: <20220616114342.3aba84ac@gandalf.local.home>
> 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
next prev parent reply other threads:[~2022-06-16 18:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 15:22 possible trace_printk() bug in v5.19-rc1 Chuck Lever III
2022-06-16 15:34 ` Steven Rostedt
2022-06-16 15:36 ` Chuck Lever III
2022-06-16 15:43 ` Steven Rostedt
2022-06-16 18:07 ` Chuck Lever III [this message]
2022-06-17 19:50 ` Steven Rostedt
2022-06-18 1:28 ` Chuck Lever III
2022-06-20 0:57 ` Chuck Lever III
2022-06-24 18:23 ` Chuck Lever III
2022-06-24 23:08 ` Steven Rostedt
2022-06-25 17:15 ` Chuck Lever III
2022-06-25 17:45 ` Steven Rostedt
2022-06-25 18:28 ` John 'Warthog9' Hawley
2022-06-26 3:01 ` John 'Warthog9' Hawley
2022-06-27 17:08 ` Chuck Lever III
2022-06-27 17:11 ` Steven Rostedt
2022-06-27 17:19 ` Chuck Lever III
2022-06-27 19:01 ` Steven Rostedt
2022-06-28 15:24 ` Steven Rostedt
2022-06-25 18:50 ` Chuck Lever III
2022-06-25 23:01 ` Steven Rostedt
2022-06-26 17:09 ` Chuck Lever III
2022-06-27 15:43 ` Steven Rostedt
2022-06-27 15:51 ` Chuck Lever III
2022-06-27 16:02 ` Steven Rostedt
2022-06-28 3:59 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88ADA44D-E457-4DA4-BD65-73F583217363@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox