linux-kernel - Re: [PATCH 04/24] x86/mm/kaiser: Unmap kernel mappings from userspace page tables, core patch

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]

Message-ID: <20171127170429.ipm3fsdzjbhlilys@pd.tnic>
Date:   Mon, 27 Nov 2017 18:04:29 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...capital.net>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H . Peter Anvin" <hpa@...or.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 04/24] x86/mm/kaiser: Unmap kernel mappings from
 userspace page tables, core patch

On Mon, Nov 27, 2017 at 04:39:07PM +0100, Peter Zijlstra wrote:
> 
> So I had the problem that I could not tell if my shiny new kernel had
> this brand spanking awesome feature enabled or not.
> 
> Do we want something like so?
> 
> ---
>  arch/x86/mm/kaiser.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/x86/mm/kaiser.c b/arch/x86/mm/kaiser.c
> index 0ff502fa655b..655349e0b5fb 100644
> --- a/arch/x86/mm/kaiser.c
> +++ b/arch/x86/mm/kaiser.c
> @@ -425,6 +425,8 @@ void __init kaiser_init(void)
>  	if (!kaiser_enabled)
>  		return;
>  
> +	pr_info("All your KAISER are belong to us.\n");
> +
>  	kaiser_init_all_pgds();
>  
>  	for_each_possible_cpu(cpu) {

Acked-by: Borislav Petkov <bp@...e.de>

And yes, the whimsical formulation is a nice touch among all those
serious dmesg spews.

:-)

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.