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: <1516011632.22147.137.camel@infradead.org>
Date:   Mon, 15 Jan 2018 11:20:32 +0100
From:   David Woodhouse <dwmw2@...radead.org>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Jon Masters <jcm@...masters.org>
Cc:     Henrique de Moraes Holschuh <hmh@....eng.br>,
        Andi Kleen <andi@...stfloor.org>, x86@...nel.org,
        linux-kernel@...r.kernel.org, pjt@...gle.com,
        torvalds@...ux-foundation.org, gregkh@...ux-foundation.org,
        peterz@...radead.org, luto@...capital.net, thomas.lendacky@....com,
        arjan.van.de.ven@...el.com
Subject: Re: Improve retpoline for Skylake

On Mon, 2018-01-15 at 11:03 +0100, Thomas Gleixner wrote:
> 
> > Our numbers on Skylake weren't bad, and there seem to be all kinds of
> > corner cases, so again, it seems as if IBRS is the safest choice.
> 
> Talk is cheap. Show numbers comparing the full retpoline/RBS mitigation
> compared to IBRS.

Right now my intent is to add IBRS support and use it by default on
Skylake instead of retpoline. Users will be able to add
'spectre_v2=retpoline' to use retpoline on Skylake instead, if they
want to. But we'll default to the safest option.

Once that is done, we can do proper comparisons, and also look at
Andi's patches to attempt to make retpoline completely safe on Skylake.
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5213 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ