Author: ken
Date: Wed Jan 23 02:28:20 2019
New Revision: 1461

Log:
Admit that the caution on the rustc page is overblown, and the purported 
mitigation does nothing.

Modified:
   html/trunk/blfs/errata/8.3-systemd/index.html
   html/trunk/blfs/errata/8.3/index.html

Modified: html/trunk/blfs/errata/8.3-systemd/index.html
==============================================================================
--- html/trunk/blfs/errata/8.3-systemd/index.html       Sun Jan  6 09:51:07 
2019        (r1460)
+++ html/trunk/blfs/errata/8.3-systemd/index.html       Wed Jan 23 02:28:20 
2019        (r1461)
@@ -18,6 +18,11 @@
        <li>In Samba, the Recommended dependency of perl module Parse::Yapp
        was mistakenly commented out.</li>
 
+       <li>On the rustc page, the caution about running tests on AMD Ryzens
+       is overstated, and the "mitigation" actually does nothing. The invalid
+       opcodes when running the tests on Ryzens are real, but the reboots were
+       almost-certainly caused by a triple-fault in the kernel - probably an
+       -rc kernel, and no doubt triggered by the invalid opcode.</li>
 <!--
        <li>The details of microcode updates, particularly for late loading,
        reflected how things used to be several kernel versions ago. This

Modified: html/trunk/blfs/errata/8.3/index.html
==============================================================================
--- html/trunk/blfs/errata/8.3/index.html       Sun Jan  6 09:51:07 2019        
(r1460)
+++ html/trunk/blfs/errata/8.3/index.html       Wed Jan 23 02:28:20 2019        
(r1461)
@@ -17,6 +17,12 @@
 
        <li>In Samba, the Recommended dependency of perl module Parse::Yapp
        was mistakenly commented out.</li>
+
+       <li>On the rustc page, the caution about running tests on AMD Ryzens
+       is overstated, and the "mitigation" actually does nothing. The invalid
+       opcodes when running the tests on Ryzens are real, but the reboots were
+       almost-certainly caused by a triple-fault in the kernel - probably an
+       -rc kernel, and no doubt triggered by the invalid opcode.</li>
      </ul>
 
      <h2>Known Security Vulnerabilities</h2>
-- 
http://lists.linuxfromscratch.org/listinfo/website
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to