Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751690AbeADAPD (ORCPT + 1 other); Wed, 3 Jan 2018 19:15:03 -0500 Received: from one.firstfloor.org ([193.170.194.197]:51530 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751394AbeADAPC (ORCPT ); Wed, 3 Jan 2018 19:15:02 -0500 Date: Wed, 3 Jan 2018 16:15:01 -0800 From: Andi Kleen To: Thomas Gleixner Cc: Andi Kleen , Linus Torvalds , Greg Kroah-Hartman , dwmw@amazon.co.uk, Tim Chen , Linux Kernel Mailing List , Dave Hansen Subject: Re: Avoid speculative indirect calls in kernel Message-ID: <20180104001501.3jof7zkrfkehnd3r@two.firstfloor.org> References: <20180103230934.15788-1-andi@firstfloor.org> <20180104000927.co5umvfzfwliqvqt@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: > It should be a CPU_BUG bit as we have for the other mess. And that can be > used for patching. It has to be done at compile time because it requires a compiler option. Most of the indirect calls are in C code. So it cannot just patched in, only partially out. -Andi