From owner-freebsd-current@freebsd.org Thu Jan 4 11:56:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E181EAD70A for ; Thu, 4 Jan 2018 11:56:29 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60BCF65D8C for ; Thu, 4 Jan 2018 11:56:28 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 4274420BE3 for ; Thu, 4 Jan 2018 06:56:22 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 04 Jan 2018 06:56:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=81/QIx ICm+eL7A5oyul8FS6yU1Ubo6R8luZKFw6JW6Q=; b=koekU0w2SQHMI4k3FMv7nS aJIPvBRYu6E7DqT/m+ZcJ5afcqvDUmAnFatnsYI9tuKFGTtr7zH+YJKAB6koWrK1 ebiNaPyfxIWBFRv7gTD2z+JwwlRhr84J8dvEFOBsCSzT51HxpKDsB37njJGg7ZZi u6b90Zx04V/tkrPnI07b6bEsLW3kz2WgRTgxkypmaHlM0S5rCRlfd2hBBEUWp0b7 2ZvsqA8fX/l6OYDmlChgS5PvYqIm7KuwaL4o1rssG3B6jPs8AYlsBfoDQSeFWbxw gBZc3S6Wm152Q2/t6kQrf8Ur96Gh/I1I45b4oBGZ466jG7NGipnFHRO+DwpKf/Ig == X-ME-Sender: Received: from [192.168.1.31] (202-129-124-76.perm.iinet.net.au [202.129.124.76]) by mail.messagingengine.com (Postfix) with ESMTPA id 903C67E2C9 for ; Thu, 4 Jan 2018 06:56:21 -0500 (EST) Subject: Re: Intel CPU design flaw - FreeBSD affected? To: freebsd-current@freebsd.org References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> From: Darren Reed Message-ID: <5A4E165B.6040809@freebsd.org> Date: Thu, 4 Jan 2018 22:56:11 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 11:56:29 -0000 On 4/01/2018 11:51 AM, Mark Heily wrote: > On Jan 2, 2018 19:05, "Warner Losh" wrote: > > The register article says the specifics are under embargo still. That would > make it hard for anybody working with Intel to comment publicly on the flaw > and any mitigations that may be underway. It would be unwise to assume that > all the details are out until the embargo lifts. > > > Details of the flaws are now published at: > > https://meltdownattack.com The web page has both: meltdown and spectre. Most people are only talking about meltdown which doesn't hit AMD. spectre impacts *both* Intel and AMD. SuSE are making available a microcode patch for AMD 17h processors that disables branch prediction: https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00004.html Kind Regards, Darren