mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Woodhouse, David" <dwmw@amazon.co.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>, <pbonzini@redhat.com>,
	<rkrcmar@redhat.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
	<hpa@zytor.com>, <dave.hansen@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
	<x86@kernel.org>, <arjan@linux.intel.com>
Subject: Re: tip/master falls off NOP cliff with KPTI under KVM
Date: Wed, 10 Jan 2018 22:53:43 +0000	[thread overview]
Message-ID: <1515624823.22302.260.camel@amazon.co.uk> (raw)
In-Reply-To: <20180110223457.GA1762@avx2>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

On Thu, 2018-01-11 at 01:34 +0300, Alexey Dobriyan wrote:
> 
> Bisection points to
> 
>         f3433c1010c6af61c9897f0f0447f81b991feac1 is the first bad commit
>         commit f3433c1010c6af61c9897f0f0447f81b991feac1
>         Author: David Woodhouse <dwmw@amazon.co.uk>
>         Date:   Tue Jan 9 14:43:11 2018 +0000
> 
>             x86/retpoline/entry: Convert entry assembler indirect jumps

Thanks. We've fixed the underlying problem with the alternatives
mechanism, *and* changed the retpoline code not to actually rely on
said fix.

> RETPOLINE is enabled but build system is reporting that compiler doesn't
> support it (Gentoo 6.4.0 p1.1)
> 
> Disabling CONFIG_RETPOLINE fixes boot.
> 
> And build system reports that "system may be insecure" even if RETPOLINE
> is disabled.

That's odd. The warning is *inside* 'ifdef CONFIG_RETPOLINE'...

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5210 bytes --]

  reply	other threads:[~2018-01-10 22:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 22:08 Alexey Dobriyan
2018-01-10 22:34 ` Alexey Dobriyan
2018-01-10 22:53   ` Woodhouse, David [this message]
2018-01-25  0:53     ` Dexuan-Linux Cui
2018-01-25  7:53       ` David Woodhouse
2018-01-25 19:00         ` Dexuan Cui
2018-01-25 19:13           ` Thomas Gleixner
2018-01-25 19:35             ` Dexuan-Linux Cui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1515624823.22302.260.camel@amazon.co.uk \
    --to=dwmw@amazon.co.uk \
    --cc=adobriyan@gmail.com \
    --cc=arjan@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome