[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180104193814.GA26859@trogon.sfo.coreos.systems>
Date: Thu, 4 Jan 2018 11:38:14 -0800
From: Benjamin Gilbert <benjamin.gilbert@...eos.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Andy Lutomirski <luto@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
linux-mm@...ck.org, stable <stable@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Garnier <thgarnie@...gle.com>,
Alexander Kuleshov <kuleshovmail@...il.com>
Subject: Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509
certs
On Thu, Jan 04, 2018 at 01:28:59PM +0100, Thomas Gleixner wrote:
> On Wed, 3 Jan 2018, Andy Lutomirski wrote:
> > Our memory map code is utter shite. This kind of bug should not be
> > possible without a giant warning at boot that something is screwed up.
>
> You're right it's utter shite and the KASLR folks who added this insanity
> of making vaddr_end depend on a gazillion of config options and not
> documenting it in mm.txt or elsewhere where it's obvious to find should
> really sit back and think hard about their half baken 'security' features.
>
> Just look at the insanity of comment above the vaddr_end ifdef maze.
>
> Benjamin, can you test the patch below please?
Seems to work!
Thanks,
--Benjamin Gilbert
Powered by blists - more mailing lists