Re: [gentoo-user] Re: New Intel CPU flaws discovered

[Dale]

Adam Carter wrote:
> On Wed, May 15, 2019 at 3:26 PM Adam Carter <adamcarter3@×××××.com
> <mailto:adamcarter3@×××××.com>> wrote:
>
>     Here we go again;
>     https://mdsattacks.com/
>
>     <snip?
>
>     Sounds like AMD not affected.
>
>
> AMD looks good;
> $ uname -a
> Linux proxy 5.1.2-gentoo #2 SMP Wed May 15 16:39:53 AEST 2019 x86_64
> AMD Phenom(tm) II X4 965 Processor AuthenticAMD GNU/Linux
> $ cat /sys/devices/system/cpu/vulnerabilities/mds
> Not affected
>
> $ uname -a
> Linux phat 5.1.2-gentoo #1 SMP Wed May 15 16:31:06 AEST 2019 x86_64
> AMD FX(tm)-8350 Eight-Core Processor AuthenticAMD GNU/Linux
> $ cat /sys/devices/system/cpu/vulnerabilities/mds
> Not affected
>
> But the skylake;
> $ uname -a
> Linux nuc 5.1.2-gentoo #2 SMP Wed May 15 16:35:17 AEST 2019 x86_64
> Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz GenuineIntel GNU/Linux
> $ cat /sys/devices/system/cpu/vulnerabilities/mds
> Mitigation: Clear CPU buffers; SMT vulnerable
>


This appears to be OK on my CPU but want to ask to be sure.   Here's
some info, sort of taking cues from what you posted above.


root@fireball / # uname -a
Linux fireball 4.18.12-gentoo #1 SMP PREEMPT Sun Oct 14 23:45:12 CDT
2018 x86_64 AMD FX(tm)-8350 Eight-Core Processor AuthenticAMD GNU/Linux
root@fireball / # cat /sys/devices/system/cpu/vulnerabilities/
l1tf               meltdown           spec_store_bypass 
spectre_v1         spectre_v2        
root@fireball / # cat /sys/devices/system/cpu/vulnerabilities/meltdown
Not affected
root@fireball / # cat /sys/devices/system/cpu/vulnerabilities/l1tf
Not affected
root@fireball / # cat
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass
Mitigation: Speculative Store Bypass disabled via prctl and seccomp
root@fireball / # cat /sys/devices/system/cpu/vulnerabilities/spectre_v1
Mitigation: __user pointer sanitization
root@fireball / # cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
Mitigation: Full AMD retpoline
root@fireball / #



Am I correct to think that "Mitigation" is good enough or does that mean
it could be affected in some other way or is risky?  Also, since the
problem that this thread is about isn't listed, mine isn't affected
correct?  I'm guessing "Not affected" means all is good.  ;-) 

Thanks much.  Just want to be sure my system is safe. 

Dale

:-)  :-)