From owner-freebsd-current@freebsd.org Sat Jan 6 10:31:55 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 E5A48EB1ADE for ; Sat, 6 Jan 2018 10:31:55 +0000 (UTC) (envelope-from k@7he.at) Received: from smtp-02.sil.at (smtp-02-5.sil.at [78.142.186.6]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A44EB6827A for ; Sat, 6 Jan 2018 10:31:54 +0000 (UTC) (envelope-from k@7he.at) Received: from mx.7he.at ([86.59.13.138]) by smtp-02.sil.at with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1eXllR-0001pI-6O; Sat, 06 Jan 2018 11:31:45 +0100 Received: from [192.168.6.60] ([93.83.242.219]) by mx.7he.at (8.15.2/8.15.2) with ESMTPS id w06AVdum045692 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 6 Jan 2018 11:31:40 +0100 (CET) (envelope-from k@7he.at) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at mx.7he.at Subject: Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC To: Michael Butler References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> <18376c97-3c0d-49c8-9483-96b95a84f3f1@7he.at> <02f1caac-b20d-d9bb-ceeb-fd1a2639e6f7@protected-networks.net> Cc: freebsd-current@freebsd.org From: "Klaus P. Ohrhallinger" Message-ID: <2dc62b9f-3ff2-227b-be0f-b3d873d332e2@7he.at> Date: Sat, 6 Jan 2018 11:31:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <02f1caac-b20d-d9bb-ceeb-fd1a2639e6f7@protected-networks.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.8 required=5.0 tests=DATE_IN_FUTURE_24_48, HELO_MISC_IP,RDNS_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mx.7he.at X-Scan-Signature: 9d02a3267670e8bb77f537b38fda5a39 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: Sat, 06 Jan 2018 10:31:56 -0000 On 04.01.2018 22:07, Michael Butler wrote: > > Interestingly, the Xeon 5400 series is not listed as vulnerable in the > Intel documentation where the 5500 and 5600s are; I checked as I have a > bunch of E5440s in service. > > https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr > Thanks for the link. Seems this was not available when I searched for a list of vulnerable CPUs. I'm not sure about Xeon W5590, it is on the list but the spectre poc does not read anything. For meltdown, somewhere in the news I read that all Intel CPUs since 1995 are vulnerable, which is rubbish. The paper says Intel CPUs since 2010. I tried different approaches to get meltdown working on Xeon E5420 and W5590 (launched Q3/2009) ... just nothing. So I am really happy that my 10 HP Proliant DL360 G5 are still safe. At least for me, a lot of panic for nothing.