linux-kernel - Re: [PATCH] arm64: Stop printing the virtual memory layout

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 15 Jan 2018 12:00:50 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Catalin Marinas <catalin.marinas@....com>
Cc:     Laura Abbott <labbott@...hat.com>,
        Mark Rutland <mark.rutland@....com>,
        Will Deacon <will.deacon@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-arm-kernel@...ts.infradead.org,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>
Subject: Re: [PATCH] arm64: Stop printing the virtual memory layout

On Mon, Jan 15, 2018 at 10:18 AM, Catalin Marinas
<catalin.marinas@....com> wrote:
> On Tue, Jan 09, 2018 at 03:02:12PM -0800, Kees Cook wrote:
>> On Tue, Dec 19, 2017 at 1:04 PM, Kees Cook <keescook@...omium.org> wrote:
>> > On Tue, Dec 19, 2017 at 11:28 AM, Laura Abbott <labbott@...hat.com> wrote:
>> >> Printing kernel addresses should be done in limited circumstances, mostly
>> >> for debugging purposes. Printing out the virtual memory layout at every
>> >> kernel bootup doesn't really fall into this category so delete the prints.
>> >> There are other ways to get the same information.
>> >
>> > In looking at this patch, I wonder: is there anything listed here that
>> > is _missing_ from CONFIG_PTDUMP? I would expect all of these to
>> > already be listed there, but I thought I'd ask...
>> >
>> > Regardless:
>> >
>> > Acked-by: Kees Cook <keescook@...omium.org>
>> >
>> > -Kees
>> >
>> >>
>> >> Signed-off-by: Laura Abbott <labbott@...hat.com>
>>
>> Did this patch get picked up? I don't see it in -next.
>
> I queued it now, should appear soon.

Great, thanks!

-Kees

-- 
Kees Cook
Pixel Security