All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-m68k <linux-m68k@vger.kernel.org>
Cc: Greg Ungerer <gerg@linux-m68k.org>,
	Kees Cook <keescook@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] m68k/mm: Stop printing the virtual memory layout
Date: Mon, 26 Feb 2018 10:46:46 +0100	[thread overview]
Message-ID: <CAMuHMdX22KBFnX_yObmb8ZBrDHtmMg9kfeDQBftcxELjGWUBpg@mail.gmail.com> (raw)
In-Reply-To: <1518425633-19803-1-git-send-email-geert@linux-m68k.org>

On Mon, Feb 12, 2018 at 9:53 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with
> %p"), the virtual memory layout printed during boot up contains "ptrval"
> instead of actual addresses:
>
>     Memory: 268040K/276480K available (2979K kernel code, 310K rwdata, 784K rodata, 144K init, 172K bss, 8440K reserved, 0K cma-reserved)
>     Virtual kernel memory layout:
>         vector  : 0x003d2e74 - 0x003d3274   (   1 KiB)
>         kmap    : 0xd0000000 - 0xf0000000   ( 512 MiB)
>         vmalloc : 0x11800000 - 0xd0000000   (3048 MiB)
>         lowmem  : 0x00000000 - 0x11000000   ( 272 MiB)
>           .init : 0x(ptrval) - 0x(ptrval)   ( 144 KiB)
>           .text : 0x(ptrval) - 0x(ptrval)   (2980 KiB)
>           .data : 0x(ptrval) - 0x(ptrval)   (1095 KiB)
>           .bss  : 0x(ptrval) - 0x(ptrval)   ( 173 KiB)
>
> Instead of changing the printing to "%px", and leaking virtual memory
> layout information again, just remove the printing completely, cfr. e.g.
> commit 071929dbdd865f77 ("arm64: Stop printing the virtual memory
> layout").
>
> All interesting information (actual section sizes) is already printed by
> mem_init_print_info() just above anyway.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>

Thanks, applied and queue for v4.17.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2018-02-26  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12  8:53 [PATCH] m68k/mm: Stop printing the virtual memory layout Geert Uytterhoeven
2018-02-13  0:48 ` Finn Thain
2018-02-13  0:48   ` Finn Thain
2018-02-13  7:34   ` Geert Uytterhoeven
2018-02-13  7:34     ` Geert Uytterhoeven
2018-02-26  9:46 ` Geert Uytterhoeven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-12  8:53 Geert Uytterhoeven

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=CAMuHMdX22KBFnX_yObmb8ZBrDHtmMg9kfeDQBftcxELjGWUBpg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.