From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-181789-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id A5C391382C5
for <garchives@archives.gentoo.org>; Thu, 4 Jan 2018 17:20:59 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 13051E097B;
Thu, 4 Jan 2018 17:20:52 +0000 (UTC)
Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 91F3CE0975
for <gentoo-user@lists.gentoo.org>; Thu, 4 Jan 2018 17:20:51 +0000 (UTC)
Received: by mail-wr0-x243.google.com with SMTP id y9so2146539wrb.5
for <gentoo-user@lists.gentoo.org>; Thu, 04 Jan 2018 09:20:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=fxwfF3/rxMr2evXDHxlbptg3JNO8o9Ipzn/fMv74pjY=;
b=I8D/pAGnoXK6BX2XCJ3Dcq4fZDnYTvD4JDFfcDdHLR5qNB7e4FFMm2cS45I9AALQtn
TlY8xjEg49reY3U2urFJmn0/CZl6lenlH9JSnFu8cXds6q75QeqYE0pVG01V/vtArZKW
mfzm/XdqshV8u/0y198ubazis0Mix19Gk0+5cc2KizTgB+FYvBC5nfmdQhbUX/i4AegU
JGGKlCHlcXVBupyIZO2h/lGC27yoQt2dJEudSjMhFqNn4b7cDzFDWl3jtTM2xX/Fz/Ac
210LmbSyb7a0unT8cSW2tH4WOzp0k2mUf00brdzEbxZhbxvR03k3hbP8NF774URKnJX8
BC7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=fxwfF3/rxMr2evXDHxlbptg3JNO8o9Ipzn/fMv74pjY=;
b=FPcsFfvlFH6jyKv6k3DBFfHd8sMfZyPb60iH39Vt6UgBv4BmlIUVAMal+CruOEb6s5
q92/KC2ETijhffsyQXf+JRum9ZurbpsdXLw6k4zXT7pYshDM3sFcgWRuE9VRVo+Ilicm
XgFnY6Lv2K+RRS8gqCXDnQNlytJLe3GPprAl25aXJzZEtRvJK0BSVmN3TnUMBkgdYpkW
kqaT9/AOeshP9Lpx/bY1wBaJ/XvGsUoaRbxdZwcSXRUtUjnj1KnC3ZUiaG1fvV3GqJkt
5aa25kGgYSM6MOB4ON6FvA3gogPuzsYIzrpbpfxUSIpocUKxBEQBbAfwnyS8rNeqg4ZU
h81Q==
X-Gm-Message-State: AKGB3mK3Mb5/AMM4ODOS+FXF/wG8HKLOOJXy01IoI7e78sh1vw+fMS/Q
AjxecB6/MJ8ZQHsluN2B4IvEi1a0xddg5Nln63FNqA==
X-Google-Smtp-Source: ACJfBovB2c3QUFC2IYPnY47lRHmEIeCzNx9mA7RgCvhYA6XoVyQXsbmLNUKJd6iT8rzOuREvp2/DjuRxs4GkvHiJYgs=
X-Received: by 10.223.177.207 with SMTP id r15mr261765wra.259.1515086450104;
Thu, 04 Jan 2018 09:20:50 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.223.164.194 with HTTP; Thu, 4 Jan 2018 09:20:49 -0800 (PST)
Received: by 10.223.164.194 with HTTP; Thu, 4 Jan 2018 09:20:49 -0800 (PST)
In-Reply-To: <43292108.BetqGqQJeV@dell_xps>
References: <23cfc7da-cdda-67ab-1e4d-b069b84ec746@sys-concept.com> <43292108.BetqGqQJeV@dell_xps>
From: "Andrey F." <ma3oxuct@gmail.com>
Date: Thu, 4 Jan 2018 09:20:49 -0800
Message-ID: <CAD7sfFwZ3g6OeSafrJx1bS3L-W6vznXyGK+cGLapQDqrTPUVwQ@mail.gmail.com>
Subject: Re: [gentoo-user] Spectre CPU flaws
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary="f403045e7de4a99e700561f68d84"
X-Archives-Salt: d9323923-14f7-4224-b355-bafa6df52f00
X-Archives-Hash: b3f3ef80bfc3a39b2476e9801082d666
--f403045e7de4a99e700561f68d84
Content-Type: text/plain; charset="UTF-8"
ALL CPUs are vulnerable to Spectre. The vuln described in your link is
Meltdown and only Intel is vulnerable to that.
https://meltdownattack.com
I don't believe there is a fix for Spectre, but it is also much tougher to
mount and attack. Meltdown on the other-hand has a fix that will likely
reduce performace, but only needs to be applied for Intel CPUs.
On Jan 4, 2018 01:46, "Mick" <michaelkintzios@gmail.com> wrote:
> On Thursday, 4 January 2018 05:50:59 GMT thelma@sys-concept.com wrote:
> > New bug resurface.
> > What is the command to test AMD CUP's if flag: X86_BUG_CPU_INSECURE is
> > enabled?
> >
> > From:
> > https://lkml.org/lkml/2017/12/27/2
>
> grep bugs /proc/cpuinfo
>
> --
> Regards,
> Mick
--f403045e7de4a99e700561f68d84
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">ALL CPUs are vulnerable to Spectre. The vuln described in=
your link is Meltdown and only Intel is vulnerable to that.=C2=A0<div dir=
=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://meltdownattack.com=
">https://meltdownattack.com</a><br></div><div dir=3D"auto"><br></div><div =
dir=3D"auto">I don't believe there is a fix for Spectre, but it is also=
much tougher to mount and attack. Meltdown on the other-hand has a fix tha=
t will likely reduce performace, but only needs to be applied for Intel CPU=
s.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Jan 4, 2018 01:46, "Mick" <<a href=3D"mailto:michaelkintzios@g=
mail.com">michaelkintzios@gmail.com</a>> wrote:<br type=3D"attribution">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Thursday, 4 January 2018 05:50:59 GMT <a =
href=3D"mailto:thelma@sys-concept.com">thelma@sys-concept.com</a> wrote:<br=
>
> New bug resurface.<br>
> What is the command to test AMD CUP's if flag: X86_BUG_CPU_INSECUR=
E is<br>
> enabled?<br>
><br>
> From:<br>
> <a href=3D"https://lkml.org/lkml/2017/12/27/2" rel=3D"noreferrer" targ=
et=3D"_blank">https://lkml.org/lkml/2017/12/<wbr>27/2</a><br>
<br>
grep bugs /proc/cpuinfo<br>
<br>
--<br>
Regards,<br>
Mick</blockquote></div></div>
--f403045e7de4a99e700561f68d84--