From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: ACJfBouOXJrx2+RPpb/pPiShSZGcUftZD09Atw5meJkeIb1a6tB7as0WNlwsEkehzGsOAtcZsLEG ARC-Seal: i=1; a=rsa-sha256; t=1515418434; cv=none; d=google.com; s=arc-20160816; b=HFvzb52ZMrCMLOpc+8zstYlni9+voxWCxv204qC28rCIYJDDCCYlelMtK/G85Aps5l 3ZUPoD9UYdztH/yJ5oahKg078RgWHvUIrG+ItgwfzlXeIxPpyZatjOlWzbSaeBZXnWfd UuWWkTPMQUiAb5AUU1IwvtY38oE3D4uq7PvmpQ8rR5421sJlwiJ21aPt4KmUEmpN65pX X/YtURju1R4zSGH1OPb0fVcDgWxxi2NQtHtp/QeyQxgH4G3EXFNAmGGOH2q7S1Xap0pi Dc/zazMJy4jgXbTGZac+HaKMOC4y32/gML7LbNnDjrejrbnt9lGySvLvGOFqJ/49slO2 0ZGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject :arc-authentication-results; bh=k94IHOupXA4xu2RHDP0Ur99z62tdTa7LVzdPlNv5sBE=; b=c9W6bWRnUuMNCG8EvnXCXgncqFjCHS/u/lZLk4f4Sfcbqni/nF+tMW15bxrRFwO5tI WxP0zf6nxp9RQDsnz1NX95lRcYFZwN/kpna31Y6dlkpPaDeXs9dIF7ysozj/M8/oZ4MF NJnsmwTOh86tIpVe3V6XdnyVR+qHDofEE1u3VQDcEGiq4WYMH+/dnpT3RpDdkP+LMgCy XI0ENXxBJGWKk04VJuCYMHBZ1yZ/BEqoLj6W+VE3Zh+OFUH8cAIqC/+oeB4VOuaG0qFW KV4Tow/EvlkSw1pbFAc04guo7hT+VUarQIYmR4Re0uyunGPECLKT6gnNno7lCruUQVPO NKDA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of arjan@linux.intel.com designates 134.134.136.65 as permitted sender) smtp.mailfrom=arjan@linux.intel.com Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of arjan@linux.intel.com designates 134.134.136.65 as permitted sender) smtp.mailfrom=arjan@linux.intel.com X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,330,1511856000"; d="scan'208";a="25387004" Subject: Re: [PATCH 00/18] prevent bounds-check bypass via speculative execution To: Bart Van Assche , "dan.j.williams@intel.com" , "linux-kernel@vger.kernel.org" Cc: "martin.petersen@oracle.com" , "hpa@zytor.com" , "peterz@infradead.org" , "pizza@shaftnet.org" , "gregkh@linuxfoundation.org" , "linux-wireless@vger.kernel.org" , "alan@linux.intel.com" , "kuznet@ms2.inr.ac.ru" , "chunkeey@googlemail.com" , "laurent.pinchart@ideasonboard.com" , "kvalo@codeaurora.org" , "ak@linux.intel.com" , "alan.cox@intel.com" , "viro@zeniv.linux.org.uk" , "linux-arch@vger.kernel.org" , "torvalds@linux-foundation.org" , "netdev@vger.kernel.org" , "davem@davemloft.net" , "arnd@arndb.de" , "edubezval@gmail.com" , "tglx@linutronix.de" , "linux-media@vger.kernel.org" , "x86@kernel.org" , "srinivas.pandruvada@linux.intel.com" , "mchehab@kernel.org" , "qla2xxx-upstream@qlogic.com" , "yoshfuji@linux-ipv6.org" , "linux-scsi@vger.kernel.org" , "jejb@linux.vnet.ibm.com" , "elena.reshetova@intel.com" , "rui.zhang@intel.com" , "jack@suse.com" , "will.deacon@arm.com" , "mingo@redhat.com" , "corbet@lwn.net" , "mark.rutland@arm.com" , "ebiederm@xmission.com" References: <151520099201.32271.4677179499894422956.stgit@dwillia2-desk3.amr.corp.intel.com> <1515386966.17218.5.camel@wdc.com> From: Arjan van de Ven Message-ID: Date: Mon, 8 Jan 2018 05:33:52 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <1515386966.17218.5.camel@wdc.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1588803914824910705?= X-GMAIL-MSGID: =?utf-8?q?1589031400761206074?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On 1/7/2018 8:49 PM, Bart Van Assche wrote: > Thank you Dan for all the work you have done on this patch series. Before > I start reviewing the patches themselves I would like to know whether or > not the issue that is addressed by this patch series could also be addressed > by AMD and Intel by modifying the CPU microcode. And if this can be > addressed by modifying the CPU microcode, will accepting this patch series > reduce the pressure on CPU manufacturers to provide such an update? unfortunately these issues cannot be addressed in a microcode update; these specific issues are very fundamental to the concept of speculation. turning off speculation is not an option ....