[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cce36f73-4381-f830-3422-1cef8ad9e622@gmail.com>
Date: Thu, 18 Jan 2018 12:03:03 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Serge Semin <fancer.lancer@...il.com>, ralf@...ux-mips.org,
miodrag.dinic@...s.com, jhogan@...nel.org, goran.ferenc@...s.com,
david.daney@...ium.com, paul.gortmaker@...driver.com,
paul.burton@...s.com, alex.belits@...ium.com,
Steven.Hill@...ium.com
Cc: alexander.sverdlin@...ia.com, matt.redfearn@...s.com,
kumba@...too.org, marcin.nowakowski@...s.com, James.hogan@...s.com,
Peter.Wotton@...s.com, Sergey.Semin@...latforms.ru,
linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 11/14] MIPS: memblock: Print out kernel virtual mem layout
On 01/17/2018 02:23 PM, Serge Semin wrote:
> It is useful to have the kernel virtual memory layout printed
> at boot time so to have the full information about the booted
> kernel. In some cases it might be unsafe to have virtual
> addresses freely visible in logs, so the %pK format is used if
> one want to hide them.
>
> Signed-off-by: Serge Semin <fancer.lancer@...il.com>
I personally like having that information because that helps debug and
have a quick reference, but there appears to be a trend to remove this
in the name of security:
https://patchwork.kernel.org/patch/10124007/
maybe hide this behind a configuration option?
--
Florian
Powered by blists - more mailing lists