From: Helge Deller <deller@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] printk-formats.txt: Add examples for %pS and %pF
Date: Tue, 15 Aug 2017 21:41:37 +0200 [thread overview]
Message-ID: <7beee4c4-6565-69ea-a220-59c83bbb6c35@gmx.de> (raw)
In-Reply-To: <20170815084654.20fc23c0@gandalf.local.home>
On 15.08.2017 14:46, Steven Rostedt wrote:
> On Thu, 10 Aug 2017 19:35:33 +0200
> Helge Deller <deller@gmx.de> wrote:
>
>> Sometimes people seems unclear when to use the %pS or %pF printk format.
>> Adding some examples may help to avoid such mistakes.
>>
>> See for example commit 51d96dc2e2dc ("random: fix warning message on ia64 and
>> parisc") which fixed such a wrong format string.
>>
>> Signed-off-by: Helge Deller <deller@gmx.de>
>>
>> diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt
>> index 65ea591..be8c05b 100644
>> --- a/Documentation/printk-formats.txt
>> +++ b/Documentation/printk-formats.txt
>> @@ -73,6 +73,12 @@ actually function descriptors which must first be resolved. The ``F`` and
>> ``f`` specifiers perform this resolution and then provide the same
>> functionality as the ``S`` and ``s`` specifiers.
>>
>> +Examples::
>> +
>> + printk("Called from %pS.\n", __builtin_return_address(0));
>> + printk("Called from %pS.\n", (void *)regs->ip);
>> + printk("Called from %pF.\n", &gettimeofday);
>
> Is the '&' really necessary?
The '&' is not necessary. The compiler doesn't complain either.
> What about using the example:
> printk("Called in %pF.\n", __func__);
Very interesting!
This code:
void smp_cpus_done() {
printk("Called from %pF.\n", smp_cpus_done);
printk("Called from %pf.\n", smp_cpus_done);
printk("Called in %pS.\n", __func__);
printk("Called in %ps.\n", __func__);
printk("Called in %pF.\n", __func__);
printk("Called in %pf.\n", __func__);
gives:
Called from smp_cpus_done+0x0/0x1b8.
Called from smp_cpus_done.
Called in __func__.28197+0x0/0x20.
Called in __func__.28197.
Called in 0x5041524953433332.
Called in 0x5041524953433332.
So, the correct usage is:
printk("Called in %pS.\n", __func__);
But it should have printed
Called from smp_cpus_done+0x0/0x1b8.
which means the (parisc?) printk resolver doesn't work correctly.
In assembly code a pointer to this object is handed to printk:
.type __func__.28197, @object
.size __func__.28197, 14
__func__.28197:
.stringz "smp_cpus_done"
I'll look into this problem.
Helge
next prev parent reply other threads:[~2017-08-15 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 17:35 Helge Deller
2017-08-11 0:15 ` Sergey Senozhatsky
2017-08-11 7:31 ` Helge Deller
2017-08-15 11:36 ` Petr Mladek
2017-08-15 19:58 ` Helge Deller
2017-08-23 14:48 ` Petr Mladek
2017-08-23 14:49 ` Steven Rostedt
2017-08-23 19:36 ` Helge Deller
2017-08-24 9:21 ` Petr Mladek
2017-08-24 0:41 ` Sergey Senozhatsky
2017-08-24 2:11 ` Steven Rostedt
2017-08-16 8:14 ` Sergey Senozhatsky
2017-08-15 12:46 ` Steven Rostedt
2017-08-15 19:41 ` Helge Deller [this message]
2017-08-15 19:47 ` Helge Deller
2017-08-15 21:35 ` 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=7beee4c4-6565-69ea-a220-59c83bbb6c35@gmx.de \
--to=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/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
all inboxes | Powered by JetHome®