Difference between revisions of "Meltdown and Spectre bugs"

From CC Doc
Jump to: navigation, search
(Marked this version for translation)
 
(2 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<translate>
 
<translate>
 
<!--T:1-->
 
<!--T:1-->
Meltdown and Spectre are bugs related to speculative execution in a variety of CPU architectures developed during the past ten to fifteen years and which affect in particular processors from Intel and AMD, including those in use on Compute Canada clusters. A detailed discussion of the two bugs can be found on [https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-every-modern-processor-has-unfixable-security-flaws/ this page]. Compute Canada personnel are currently patching systems deemed sensitive to these vulnerabilities.  
+
Meltdown and Spectre are bugs related to speculative execution in a variety of CPU architectures developed during the past ten to fifteen years and which affect in particular processors from Intel and AMD, including those in use on Compute Canada clusters. A detailed discussion of the two bugs can be found on [https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-every-modern-processor-has-unfixable-security-flaws/ this page]. Compute Canada personnel have patched systems deemed sensitive to these vulnerabilities.  
  
 
== What are the impacts ? == <!--T:2-->
 
== What are the impacts ? == <!--T:2-->
 
=== Availability impacts ===
 
=== Availability impacts ===
Updates to patch the vulnerabilities require updating the operating system and rebooting the nodes. For compute nodes, this is typically done in a rolling fashion, resulting in nodes being unavailable for a short period of time. This may impair the scheduling of large jobs, but typically goes unnoticed by users. Some nodes, such as login nodes and cloud hosts, will however see a short interruption of service.
+
Updates to patch the vulnerabilities required updating the operating system and rebooting the nodes. For compute nodes this was typically done in a rolling fashion, was largely transparent to users, and is now complete.
 +
 
 +
<!--T:11-->
 +
Updates were applied at [[Graham]] between 2018 January 5 and January 31. Most nodes were updated by January 13.
  
 
=== Performance impacts === <!--T:3-->
 
=== Performance impacts === <!--T:3-->
Many groups around the world, including within Compute Canada, are running benchmarks to evaluate the effects of the operating system patches on performance. Certain figures that have been cited are alarming (up to a 30% or even 50% performance hit), while others are very minimal.
+
Many groups around the world have run benchmarks to evaluate the effects of the operating system patches on performance. Certain figures that have been cited are alarming (up to a 30% or even 50% performance hit), while others are very minimal.
  
 
<!--T:4-->
 
<!--T:4-->
Line 19: Line 22:
  
 
== What is Compute Canada doing about it ? == <!--T:6-->
 
== What is Compute Canada doing about it ? == <!--T:6-->
Teams managing the Compute Canada clusters are acting diligently to update their servers as needed and as patches are released by various vendors. Many servers have already been patched, but some may require more updates as vendors release new patches.
+
All vulnerable equipment operated by Compute Canada has been patched. If and when vendors release new patches, these will also be applied.
  
 
== What should I do about it ? == <!--T:7-->
 
== What should I do about it ? == <!--T:7-->
Line 28: Line 31:
  
 
=== I have a virtual machine running on the Compute Canada Cloud === <!--T:9-->
 
=== I have a virtual machine running on the Compute Canada Cloud === <!--T:9-->
Update your virtual machine's operating system to the latest version frequently over the coming days to ensure it has the latest security patches to address these bugs. See [[Security_considerations_when_running_a_VM#Updating_your_VM|updating your VM]] for specific instructions on how to update Linux VMs.
+
Update your virtual machine's operating system to the latest version frequently to ensure it has the latest security patches to address these bugs. See [[Security_considerations_when_running_a_VM#Updating_your_VM|updating your VM]] for specific instructions on how to update Linux VMs.
  
 
== References == <!--T:10-->
 
== References == <!--T:10-->
Line 39: Line 42:
 
* [https://access.redhat.com/articles/3311301 Controlling the Performance Impact of Microcode and Security Patches for CVE-2017-5754 CVE-2017-5715 and CVE-2017-5753 using Red Hat Enterprise Linux Tunables]
 
* [https://access.redhat.com/articles/3311301 Controlling the Performance Impact of Microcode and Security Patches for CVE-2017-5754 CVE-2017-5715 and CVE-2017-5753 using Red Hat Enterprise Linux Tunables]
 
* [https://access.redhat.com/labs/speculativeexecution/ Red Hat's Spectre and Meltdown detector tool]
 
* [https://access.redhat.com/labs/speculativeexecution/ Red Hat's Spectre and Meltdown detector tool]
 +
* [https://arxiv.org/pdf/1801.04329.pdf Effect of Meltdown and Spectre Patches on the Performance of HPC Applications]
 
</translate>
 
</translate>

Latest revision as of 14:41, 12 March 2018

Other languages:
English • ‎français

Meltdown and Spectre are bugs related to speculative execution in a variety of CPU architectures developed during the past ten to fifteen years and which affect in particular processors from Intel and AMD, including those in use on Compute Canada clusters. A detailed discussion of the two bugs can be found on this page. Compute Canada personnel have patched systems deemed sensitive to these vulnerabilities.

What are the impacts ?

Availability impacts

Updates to patch the vulnerabilities required updating the operating system and rebooting the nodes. For compute nodes this was typically done in a rolling fashion, was largely transparent to users, and is now complete.

Updates were applied at Graham between 2018 January 5 and January 31. Most nodes were updated by January 13.

Performance impacts

Many groups around the world have run benchmarks to evaluate the effects of the operating system patches on performance. Certain figures that have been cited are alarming (up to a 30% or even 50% performance hit), while others are very minimal.

Tasks which involve a lot of input/output (reading and writing files) seem to be most heavily affected. Examples include databases, or file transfers (e.g. rsync). Most high performance computing jobs should be minimally affected since the vast majority of the run time is spent computing rather than doing input and output. Different processor generations are also affected to different degrees, with the most notable performance degradation reported for older processors.

In the References section below you will find links to some recent performance comparisons. Keep in mind that these were not necessarily run on hardware and operating systems similar to what Compute Canada clusters are running.

What is Compute Canada doing about it ?

All vulnerable equipment operated by Compute Canada has been patched. If and when vendors release new patches, these will also be applied.

What should I do about it ?

Security-wise, please rest assured that Compute Canada team members are taking every action possible to ensure that systems we run are secure. If you are operating your own virtual machine in our cloud, you are however responsible for updating its operating system to include the latest security patches (see next subsection).

Performance-wise, if you believe that your application may be severely impacted by the security patches, please contact our Technical support team. We encourage you to bring forward comparative performance numbers of your application (job run times before and after the announcement, for example). Keep in mind however that mitigating the performance impact of the security patches is likely to require some modification to the code you are running, and may not always be possible.

I have a virtual machine running on the Compute Canada Cloud

Update your virtual machine's operating system to the latest version frequently to ensure it has the latest security patches to address these bugs. See updating your VM for specific instructions on how to update Linux VMs.

References