[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+h9RKAND8+SJR6P6CQY_YO3ezjsnfuzLGsQbY=O4XCuw@mail.gmail.com>
Date: Tue, 22 Jan 2019 09:42:13 +1300
From: Kees Cook <keescook@...omium.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Andi Kleen <ak@...ux.intel.com>, Julian Stecklina <jsteckli@...zon.de>,
LKML <linux-kernel@...r.kernel.org>, David Woodhouse <dwmw2@...radead.org>,
Liran Alon <liran.alon@...cle.com>, Paolo Bonzini <pbonzini@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>, Linus Torvalds <torvalds@...ux-foundation.org>,
X86 ML <x86@...nel.org>, Kernel Hardening <kernel-hardening@...ts.openwall.com>
Subject: Re: [RFC] x86/speculation: add L1 Terminal Fault / Foreshadow demo
On Tue, Jan 22, 2019 at 8:15 AM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Mon, Jan 21, 2019 at 10:36:18AM -0800, Andi Kleen wrote:
> > > + /* Check the start address: needs to be page-aligned.. */
> > > +- if (start & ~PAGE_MASK)
> > > ++ if (start & ~PAGE_MASK) {
> > > ++
> > > ++ /*
> > > ++ * XXX Hack
> > > ++ *
> > > ++ * We re-use this error case to show case a cache load gadget:
> > > ++ * There is a mispredicted branch, which leads to prefetching
> > > ++ * the cache with attacker controlled data.
> > > ++ */
> > > ++ asm volatile (
> >
> > Obviously that can never be added to a standard kernel.
>
> No, that's why it is a patch, right? People want to test things, it's
> nice to have a way to easily do this.
What about adding something like it to drivers/misc/lkdtm/ instead?
It's not a "production" module, but it regularly get built for selftest builds.
--
Kees Cook
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
