From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zCB6c5LQ1zDqHD for ; Fri, 5 Jan 2018 02:09:42 +1100 (AEDT) From: Christian Zigotzky Content-Type: multipart/alternative; boundary=Apple-Mail-CAE8A674-3DEF-4FAA-8865-BC8F6CCD5AC1 Mime-Version: 1.0 (1.0) Date: Thu, 4 Jan 2018 16:09:34 +0100 Subject: Spectre+Meltdown Message-Id: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> To: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --Apple-Mail-CAE8A674-3DEF-4FAA-8865-BC8F6CCD5AC1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hi All, Do we have some information regarding Spectre+Meltdown for our users? It could be that we have some security issues in our PowerPC CPUs. Links: https://www.phoronix.com/scan.php?page=3Dnews_item&px=3DLinux-Kernel-Retpoli= ne-Patches https://www.phoronix.com/scan.php?page=3Dnews_item&px=3Dx86-PTI-EPYC-Linux-4= .15-Test Thanks, Christian Sent from my iPhone= --Apple-Mail-CAE8A674-3DEF-4FAA-8865-BC8F6CCD5AC1 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi All,

Do we have some information regarding Spectre+Meltdow= n for our users?

It could be that we have some security issues in our Pow= erPC CPUs.

Links:



Sent from my= iPhone
= --Apple-Mail-CAE8A674-3DEF-4FAA-8865-BC8F6CCD5AC1-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zCLV50Dm0zDqmy for ; Fri, 5 Jan 2018 08:27:08 +1100 (AEDT) Date: Thu, 4 Jan 2018 22:27:04 +0100 From: Michal =?UTF-8?B?U3VjaMOhbmVr?= To: Christian Zigotzky Cc: linuxppc-dev@lists.ozlabs.org Subject: Re: Spectre+Meltdown Message-ID: <20180104222704.5a9b490d@naga.suse.cz> In-Reply-To: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello, On Thu, 4 Jan 2018 16:09:34 +0100 Christian Zigotzky wrote: > Hi All, > > Do we have some information regarding Spectre+Meltdown for our users? > > It could be that we have some security issues in our PowerPC CPUs. > > Links: > > https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Retpoline-Patches > > https://www.phoronix.com/scan.php?page=news_item&px=x86-PTI-EPYC-Linux-4.15-Test > Since the vulnerability details were disclosed already you should see patches addressing it in your local kernel git repository. AFAICT some patches for preventing speculative execution in some random parts of the kernel as well as adding an extra flush when returning from kernel to userspace are applicable to powerpc. I am not familiar with all the details so you are free to investigate the code for yourself or fish some article from someone who really knows what the thing is all about and how it affects powerpc in particular. Thanks Michal From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (bilbo.ozlabs.org [103.22.144.67]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zDGZs2Gm8zF0Rg for ; Sat, 6 Jan 2018 20:34:29 +1100 (AEDT) From: Michael Ellerman To: Christian Zigotzky , linuxppc-dev@lists.ozlabs.org Subject: Re: Spectre+Meltdown In-Reply-To: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> Date: Sat, 06 Jan 2018 20:34:28 +1100 Message-ID: <874lnzz5y3.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Christian Zigotzky writes: > Hi All, > > Do we have some information regarding Spectre+Meltdown for our users? > > It could be that we have some security issues in our PowerPC CPUs. There's a statement from IBM here: https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/ I think you're mostly using pasemi CPUs right? I don't have any information on them, and obviously it's going to be hard to find anyone who might know. You might be best finding a proof of concept somewhere and actually testing it. cheers From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zDzCG5yG2zF0R6 for ; Mon, 8 Jan 2018 00:04:58 +1100 (AEDT) Subject: Spectre+Meltdown To: Michael Ellerman , linuxppc-dev@lists.ozlabs.org, Olof Johansson References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> From: Christian Zigotzky Message-ID: <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> Date: Sun, 7 Jan 2018 14:04:40 +0100 MIME-Version: 1.0 In-Reply-To: <874lnzz5y3.fsf@concordia.ellerman.id.au> Content-Type: text/plain; charset=utf-8; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello Michael, Thanks for your reply. We are using P.A. Semi and Freescale CPUs. @Olof Do you have some infos for us? Thanks, Christian On 06/01/18 10:34, Michael Ellerman wrote: > Christian Zigotzky writes: > >> Hi All, >> >> Do we have some information regarding Spectre+Meltdown for our users? >> >> It could be that we have some security issues in our PowerPC CPUs. > There's a statement from IBM here: > > https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/ > > > I think you're mostly using pasemi CPUs right? I don't have any > information on them, and obviously it's going to be hard to find anyone > who might know. You might be best finding a proof of concept somewhere > and actually testing it. > > cheers > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zF6yF2Ft7zF0Rm for ; Mon, 8 Jan 2018 05:54:10 +1100 (AEDT) Received: by mail-lf0-x235.google.com with SMTP id h137so9973408lfe.8 for ; Sun, 07 Jan 2018 10:54:10 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> From: Olof Johansson Date: Sun, 7 Jan 2018 10:54:04 -0800 Message-ID: Subject: Re: Spectre+Meltdown To: Christian Zigotzky Cc: Michael Ellerman , linuxppc-dev Content-Type: text/plain; charset="UTF-8" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky wrote: > Hello Michael, > > Thanks for your reply. We are using P.A. Semi and Freescale CPUs. > > @Olof > Do you have some infos for us? I'm low on spare time to experiment and explore what might be exposed or not, and I no longer have any proprietary microarchitecture documentation of the core. I suggest reaching out to your supplier of the silicon for commercial support and information, or just going with what I'm sure will be architecturally generic solutions to the problem when IBM has them ready. -Olof From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zFHPR2wF7zF0Pr for ; Mon, 8 Jan 2018 12:14:50 +1100 (AEDT) Received: by mail-lf0-x232.google.com with SMTP id w23so312489lfd.11 for ; Sun, 07 Jan 2018 17:14:50 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> From: Michal Suchanek Date: Mon, 8 Jan 2018 02:14:06 +0100 Message-ID: Subject: Re: Spectre+Meltdown To: Olof Johansson Cc: Christian Zigotzky , linuxppc-dev Content-Type: text/plain; charset="UTF-8" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 7 January 2018 at 19:54, Olof Johansson wrote: > On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky > wrote: >> Hello Michael, >> >> Thanks for your reply. We are using P.A. Semi and Freescale CPUs. >> >> @Olof >> Do you have some infos for us? > > I'm low on spare time to experiment and explore what might be exposed > or not, and I no longer have any proprietary microarchitecture > documentation of the core. > > I suggest reaching out to your supplier of the silicon for commercial > support and information, or just going with what I'm sure will be > architecturally generic solutions to the problem when IBM has them > ready. The solution for IBM POWER involves patching the firmware as well as Linux. Without knowledge of the architecture specifics it is not possible to tell if other cores are affected and if the measures implemented by IBM can be used. In fact they probably rely on 64s-specific instructions and are in part implemented in 64s-specific assembly files. So this will not work without support for the specific core either by the vendor or somebody who has knowledge of the architecture details. Thanks Michal From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zFSmp5sGgzF0RS for ; Mon, 8 Jan 2018 19:17:12 +1100 (AEDT) Subject: Spectre+Meltdown To: Michal Suchanek , Olof Johansson Cc: linuxppc-dev References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> From: Christian Zigotzky Message-ID: <32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de> Date: Mon, 8 Jan 2018 09:17:05 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi All, Thanks a lot for your replies. @NXP developers: Could you please tell us some information? Thanks, Christian On 08 January 2018 at 02:14AM, Michal Suchanek wrote: > On 7 January 2018 at 19:54, Olof Johansson wrote: >> On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky >> wrote: >>> Hello Michael, >>> >>> Thanks for your reply. We are using P.A. Semi and Freescale CPUs. >>> >>> @Olof >>> Do you have some infos for us? >> I'm low on spare time to experiment and explore what might be exposed >> or not, and I no longer have any proprietary microarchitecture >> documentation of the core. >> >> I suggest reaching out to your supplier of the silicon for commercial >> support and information, or just going with what I'm sure will be >> architecturally generic solutions to the problem when IBM has them >> ready. > The solution for IBM POWER involves patching the firmware as well as > Linux. Without knowledge of the architecture specifics it is not > possible to tell if other cores are affected and if the measures > implemented by IBM can be used. In fact they probably rely on > 64s-specific instructions and are in part implemented in 64s-specific > assembly files. > > So this will not work without support for the specific core either by > the vendor or somebody who has knowledge of the architecture details. > > Thanks > > Michal > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f177.google.com (mail-io0-f177.google.com [209.85.223.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zH5q14t0lzF0VX for ; Thu, 11 Jan 2018 11:09:49 +1100 (AEDT) Received: by mail-io0-f177.google.com with SMTP id 25so1348426ioj.9 for ; Wed, 10 Jan 2018 16:09:49 -0800 (PST) Received: from mail-io0-f169.google.com (mail-io0-f169.google.com. [209.85.223.169]) by smtp.gmail.com with ESMTPSA id 103sm10723151ioj.74.2018.01.10.16.09.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 16:09:46 -0800 (PST) Received: by mail-io0-f169.google.com with SMTP id z130so1341785ioe.13 for ; Wed, 10 Jan 2018 16:09:46 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de> References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> <32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de> From: Li Yang Date: Wed, 10 Jan 2018 18:09:45 -0600 Message-ID: Subject: Re: Spectre+Meltdown To: Christian Zigotzky Cc: Michal Suchanek , Olof Johansson , linuxppc-dev Content-Type: text/plain; charset="UTF-8" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Jan 8, 2018 at 2:17 AM, Christian Zigotzky wrote: > Hi All, > > Thanks a lot for your replies. > > @NXP developers: Could you please tell us some information? We have done some investigation but it is not ready to be published yet. You can get more information from your support channel right now. > > Thanks, > Christian > > > > On 08 January 2018 at 02:14AM, Michal Suchanek wrote: >> >> On 7 January 2018 at 19:54, Olof Johansson wrote: >>> >>> On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky >>> wrote: >>>> >>>> Hello Michael, >>>> >>>> Thanks for your reply. We are using P.A. Semi and Freescale CPUs. >>>> >>>> @Olof >>>> Do you have some infos for us? >>> >>> I'm low on spare time to experiment and explore what might be exposed >>> or not, and I no longer have any proprietary microarchitecture >>> documentation of the core. >>> >>> I suggest reaching out to your supplier of the silicon for commercial >>> support and information, or just going with what I'm sure will be >>> architecturally generic solutions to the problem when IBM has them >>> ready. >> >> The solution for IBM POWER involves patching the firmware as well as >> Linux. Without knowledge of the architecture specifics it is not >> possible to tell if other cores are affected and if the measures >> implemented by IBM can be used. In fact they probably rely on >> 64s-specific instructions and are in part implemented in 64s-specific >> assembly files. >> >> So this will not work without support for the specific core either by >> the vendor or somebody who has knowledge of the architecture details. >> >> Thanks >> >> Michal >> > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=FROM_EXCESS_BASE64, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E08E0C43441 for ; Fri, 23 Nov 2018 19:02:08 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3EFA620824 for ; Fri, 23 Nov 2018 19:02:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3EFA620824 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 431lzd56sSzDqLT for ; Sat, 24 Nov 2018 06:02:05 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=suse.de (client-ip=195.135.220.15; helo=mx1.suse.de; envelope-from=msuchanek@suse.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=suse.de Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 431lxF2Gt8zDqWv for ; Sat, 24 Nov 2018 05:59:59 +1100 (AEDT) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 7EB91AD73; Fri, 23 Nov 2018 18:59:56 +0000 (UTC) Date: Fri, 23 Nov 2018 19:59:55 +0100 From: Michal =?UTF-8?B?U3VjaMOhbmVr?= To: Li Yang Subject: Re: Spectre+Meltdown Message-ID: <20181123195955.1bdcdd80@kitsune.suse.cz> In-Reply-To: References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> <32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de> Organization: SUSE Linux X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.31; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Olof Johansson , Michal Suchanek , linuxppc-dev , Christian Zigotzky Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Wed, 10 Jan 2018 18:09:45 -0600 Li Yang wrote: Hello, > On Mon, Jan 8, 2018 at 2:17 AM, Christian Zigotzky > wrote: > > Hi All, > > > > Thanks a lot for your replies. > > > > @NXP developers: Could you please tell us some information? > > We have done some investigation but it is not ready to be published > yet. You can get more information from your support channel right > now. With this summary paper https://arxiv.org/abs/1811.05441 it should be possible to take the manual for your favourite CPU and see which exploitable optimizations it does have, and how are these exploits mitigated. Thanks Michal From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 60F21C43441 for ; Sat, 24 Nov 2018 09:17:04 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E713D20865 for ; Sat, 24 Nov 2018 09:17:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=xenosoft.de header.i=@xenosoft.de header.b="mau90dxG" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E713D20865 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xenosoft.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4326y45cV4zDqVf for ; Sat, 24 Nov 2018 20:17:00 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=xenosoft.de Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=xenosoft.de header.i=@xenosoft.de header.b="mau90dxG"; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (helo) smtp.helo=mo6-p00-ob.smtp.rzone.de (client-ip=2a01:238:20a:202:5300::7; helo=mo6-p00-ob.smtp.rzone.de; envelope-from=chzigotzky@xenosoft.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=xenosoft.de Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=xenosoft.de header.i=@xenosoft.de header.b="mau90dxG"; dkim-atps=neutral Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4326vG2hB8zDqVh for ; Sat, 24 Nov 2018 20:14:32 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1543050867; s=strato-dkim-0002; d=xenosoft.de; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=3n/TtzjGoQrGXHflw0tnMyPSBEQoLAM/2BS54S5TrSs=; b=mau90dxGIabrbbgufxYuLUNc91dl9AXc5f6JLHFy/u7gFcQSu+7h2+e7stZAP4ai3r tBCWP0sJi1fSUesy2IptnClG65ITAmNNVT4KsCo0+PWqyPt5QXDM7yr+N74FtSTkfELN P6W/joDpl9CJxrrH6MgM9P114q6G3C+cKM5wsTpNY+7pokVufPnvidvj1H6l1ICeHkkF 6RQr2g8U1kzSndzbHaQDdiw6beDS0WlYNVkFZKD6N3/FlRYC6Gf8IkbPcmFMu7WTVjcr +QqsYYU7/lTmvABukXP2YzrzzoZT0F+5WpJpYgb/7T/Ax1tU5fQOnkllsdDszVaLMvK3 3EjA== X-RZG-AUTH: ":L2QefEenb+UdBJSdRCXu93KJ1bmSGnhMdmOod1DhGN0rBVhd9dFr6Kxrf+5Dj7x4Ql+BpvNtdS8exnpinP0JAbBX8S5TJng6d4MbmVgn" X-RZG-CLASS-ID: mo00 Received: from [IPv6:2a02:8109:a400:162c:b95b:477:b06f:4eba] by smtp.strato.de (RZmta 44.4 AUTH) with ESMTPSA id L01e52uAO9EGABH (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Sat, 24 Nov 2018 10:14:16 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Spectre+Meltdown From: Christian Zigotzky X-Mailer: iPhone Mail (15G77) In-Reply-To: <20181123195955.1bdcdd80@kitsune.suse.cz> Date: Sat, 24 Nov 2018 10:14:14 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7D1BF717-CF1C-45CC-89B3-01D6590C6A31@xenosoft.de> References: <36E75811-C758-49B1-8E5C-3A2C44FD5DE9@xenosoft.de> <874lnzz5y3.fsf@concordia.ellerman.id.au> <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> <32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de> <20181123195955.1bdcdd80@kitsune.suse.cz> To: =?utf-8?Q?Michal_Such=C3=A1nek?= X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Olof Johansson , Michal Suchanek , linuxppc-dev , Li Yang Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On 23. Nov 2018, at 19:59, Michal Such=C3=A1nek wrote: With this summary paper https://arxiv.org/abs/1811.05441 it should be possible to take the manual for your favourite CPU and see which exploitable optimizations it does have, and how are these exploits mitigated. Thanks Michal Hi Michal, Thanks for the hint. Here is the status of our machines: FYI: X1000, CPU: PWRficient PA6T-1682M, kernel 4.20-rc3: grep . /sys/devices/syst= em/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected /sys/devices/system/cpu/vulnerabilities/meltdown:Vulnerable /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointe= r sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software coun= t cache flush -------- X5000/020, CPU: P5020 (e5500), kernel 4.20-rc3: grep . /sys/devices/system/c= pu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Not affected /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointe= r sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software coun= t cache flush The PA6T is still vulnerable. Cheers, Christian=