Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: labbott@redhat.com (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH] arm64: Switch to %px for printing some addresses at bootup
Date: Thu, 14 Dec 2017 15:30:44 -0800	[thread overview]
Message-ID: <1ae091cb-c88f-4d05-a860-9ee6a8d5ffc3@redhat.com> (raw)
In-Reply-To: <CAGXu5jK1H1+VSENq9uVGJsqOkB42WvZuRviyPpSmgywUmXte8A@mail.gmail.com>

On 12/14/2017 02:51 PM, Kees Cook wrote:
> On Thu, Dec 14, 2017 at 2:39 PM, Laura Abbott <labbott@redhat.com> wrote:
>> With the move to stricter %p printing, several of the addresses
>> are no longer printed out. Switch to %px so they always get printed.
>>
>> Signed-off-by: Laura Abbott <labbott@redhat.com>
>> ---
>> I'll admit to finding the new %p restrictions particularly irritating
>> here because I like seeing the print out of the virtual addresses for
>> debugging and checking. It might also be worth discussing whether we
>> should be printing anything out?
> 
> If they're always printed at boot, I think they should likely be removed...
> 
> -Kees
> 

Yeah, I suspected as much. I'll submit a patch to just remove it
unless someone has a counter proposal.

Thanks,
Laura

>> ---
>>   arch/arm64/mm/init.c | 10 +++++-----
>>   1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
>> index 5960bef0170d..9be53e050f50 100644
>> --- a/arch/arm64/mm/init.c
>> +++ b/arch/arm64/mm/init.c
>> @@ -613,15 +613,15 @@ void __init mem_init(void)
>>                  MLM(MODULES_VADDR, MODULES_END));
>>          pr_notice("    vmalloc : 0x%16lx - 0x%16lx   (%6ld GB)\n",
>>                  MLG(VMALLOC_START, VMALLOC_END));
>> -       pr_notice("      .text : 0x%p" " - 0x%p" "   (%6ld KB)\n",
>> +       pr_notice("      .text : 0x%px" " - 0x%px" "   (%6ld KB)\n",
>>                  MLK_ROUNDUP(_text, _etext));
>> -       pr_notice("    .rodata : 0x%p" " - 0x%p" "   (%6ld KB)\n",
>> +       pr_notice("    .rodata : 0x%px" " - 0x%px" "   (%6ld KB)\n",
>>                  MLK_ROUNDUP(__start_rodata, __init_begin));
>> -       pr_notice("      .init : 0x%p" " - 0x%p" "   (%6ld KB)\n",
>> +       pr_notice("      .init : 0x%px" " - 0x%px" "   (%6ld KB)\n",
>>                  MLK_ROUNDUP(__init_begin, __init_end));
>> -       pr_notice("      .data : 0x%p" " - 0x%p" "   (%6ld KB)\n",
>> +       pr_notice("      .data : 0x%px" " - 0x%px" "   (%6ld KB)\n",
>>                  MLK_ROUNDUP(_sdata, _edata));
>> -       pr_notice("       .bss : 0x%p" " - 0x%p" "   (%6ld KB)\n",
>> +       pr_notice("       .bss : 0x%px" " - 0x%px" "   (%6ld KB)\n",
>>                  MLK_ROUNDUP(__bss_start, __bss_stop));
>>          pr_notice("    fixed   : 0x%16lx - 0x%16lx   (%6ld KB)\n",
>>                  MLK(FIXADDR_START, FIXADDR_TOP));
>> --
>> 2.14.3
>>
> 
> 
> 

      reply	other threads:[~2017-12-14 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 22:39 [RFC][PATCH] arm64: Switch to %px for printing some addresses at bootup Laura Abbott
2017-12-14 22:51 ` Kees Cook
2017-12-14 23:30   ` Laura Abbott [this message]

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=1ae091cb-c88f-4d05-a860-9ee6a8d5ffc3@redhat.com \
    --to=labbott@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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