Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751832AbeADAUF (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Wed, 3 Jan 2018 19:20:05 -0500
Received: from mail-io0-f182.google.com ([209.85.223.182]:42302 "EHLO
        mail-io0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751237AbeADAUE (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 3 Jan 2018 19:20:04 -0500
X-Google-Smtp-Source: ACJfBouoonqXixk0yX9rBzJXxc4vXO9ttVOH+WEOi+3eYWC9kbwz8kdHmDwnY+Q+uP5gfi8hpLPq+17CvBwQrrAzbv4=
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1801040110440.1957@nanos>
References: <20180103230934.15788-1-andi@firstfloor.org> <CA+55aFzCocoK+4kxAUEhaxxba4RTv3ewBmhiZ8Osc9iDkBtCEQ@mail.gmail.com>
 <20180104000927.co5umvfzfwliqvqt@two.firstfloor.org> <alpine.DEB.2.20.1801040110440.1957@nanos>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed, 3 Jan 2018 16:20:02 -0800
X-Google-Sender-Auth: lDBKgf4Hm92KhSi5xSh2nw05kkY
Message-ID: <CA+55aFwOqb7F+iP8xC5wTt3Cigj81XguQbLKAVhNg01L2OGhjg@mail.gmail.com>
Subject: Re: Avoid speculative indirect calls in kernel
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>,
        Greg Kroah-Hartman <gregkh@linux-foundation.org>,
        dwmw@amazon.co.uk, Tim Chen <tim.c.chen@linux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Dave Hansen <dave.hansen@intel.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

On Wed, Jan 3, 2018 at 4:12 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> It should be a CPU_BUG bit as we have for the other mess. And that can be
> used for patching.

That would definitely be the right approach.

However, that's also probably quite challenging for the gcc option.

              Linus