From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753035AbcFNUzP (ORCPT ); Tue, 14 Jun 2016 16:55:15 -0400 Received: from terminus.zytor.com ([198.137.202.10]:48854 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752205AbcFNUzN (ORCPT ); Tue, 14 Jun 2016 16:55:13 -0400 Subject: Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak To: Borislav Petkov References: <7FB15233-B347-4A87-9506-A9E10D331292@gmail.com> <1465923672-14232-1-git-send-email-lukasz.anaczkowski@intel.com> <57603DC0.9070607@linux.intel.com> <20160614193407.1470d998@lxorguk.ukuu.org.uk> <576052E0.3050408@linux.intel.com> <20160614191916.GI30015@pd.tnic> <4b2c481e-35ae-1cd6-ca58-1535bfef346c@zytor.com> <20160614204736.GL30015@pd.tnic> Cc: Dave Hansen , One Thousand Gnomes , Lukasz Anaczkowski , linux-kernel@vger.kernel.org, linux-mm@kvack.org, tglx@linutronix.de, mingo@redhat.com, ak@linux.intel.com, kirill.shutemov@linux.intel.com, mhocko@suse.com, akpm@linux-foundation.org, harish.srinivasappa@intel.com, lukasz.odzioba@intel.com, grzegorz.andrejczuk@intel.com, lukasz.daniluk@intel.com From: "H. Peter Anvin" Message-ID: Date: Tue, 14 Jun 2016 13:54:25 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160614204736.GL30015@pd.tnic> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/14/16 13:47, Borislav Petkov wrote: > On Tue, Jun 14, 2016 at 01:20:06PM -0700, H. Peter Anvin wrote: >> static_cpu_has_bug() should turn into 5-byte NOP in the common (bugless) >> case. > > Yeah, it does. I looked at the asm. > > I wasn't 100% sure because I vaguely remember gcc reordering things in > some pathological case but I'm most likely remembering wrong because if > it were doing that, then the whole nopping out won't work. F'get about > it. :) > There was that. It is still possible that we end up with NOP a JMP right before another JMP; we could perhaps make the patching code smarter and see if we have a JMP immediately after. -hpa