caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] [IMPORTANT] Intel Skylake / Kaby Lake hardware bug affects OCaml programs
Date: Fri, 30 Jun 2017 15:51:11 +0200	[thread overview]
Message-ID: <0ea087b1-7267-eee6-3dd5-55a760d8f4cd@inria.fr> (raw)

Dear OCaml users,

It was recently made public that Intel processors of the Skylake and Kaby Lake families have a nasty hardware bug concerning hyperthreading.  See, for example
https://arstechnica.com/information-technology/2017/06/skylake-kaby-lake-chips-have-a-crash-bug-with-hyperthreading-enabled/

I wanted to draw the attention of all OCaml users to this issue, because this hardware bug is triggered by the OCaml runtime under fairly common conditions.  Random crashes caused by this bug were observed at Ahrefs and another industrial user of OCaml, and also by users of Coccinelle and of Coq.  (*)

Your OCaml installation may be affected if the following three conditions are met:

1- You're using an Intel processor of the Skylake or Kaby Lake family.
   (AMD processors and older Intel processors are not affected.)
   
2- The processor support hyperthreading (HT) and hyperthreading is enabled in the BIOS.

3- The OCaml runtime system was compiled with certain versions of GCC.
   (We don't know exactly which versions of GCC triggers the issue, but
    it seems that it is never triggered by clang-generated code.
    In particular, this means that Mac OS X users should be safe.)

See https://lists.debian.org/debian-devel/2017/06/msg00308.html for help in determining if your processor is vulnerable, and for instructions on how to address the issue.  Possible fixes include:

- Apply the microcode update recently released by Intel for Skylake processors.  (No such update exists yet for Kaby Lake processors.)
- Disable hyperthreading in the BIOS.
- Reinstall OCaml using clang instead of GCC.

Kind regards,

- Xavier Leroy

(*) It is likely that we OCaml folks were the first to pinpoint this Intel bug.  For more information, see the narratives at
https://caml.inria.fr/mantis/view.php?id=7452
https://medium.com/ahrefs/skylake-bug-a-detective-story-ab1ad2beddcd

             reply	other threads:[~2017-06-30 13:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30 13:51 Xavier Leroy [this message]
2017-06-30 14:15 ` Xavier Leroy
2017-06-30 15:17   ` Gabriel Scherer
2017-06-30 15:31     ` Emilio Jesús Gallego Arias
2017-06-30 16:30     ` Julia Lawall
2017-06-30 16:46       ` Anton Bachin
2017-06-30 17:03         ` Xavier Leroy
2017-07-05  1:01     ` Johannes Kanig
2017-06-30 15:28   ` Mark Shinwell
2017-06-30 15:19 ` Maxime Dénès
2017-06-30 15:38   ` Anton Bachin
2017-07-21 13:00 ` David MENTRÉ
2017-07-22  7:27   ` Gabriel Scherer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ea087b1-7267-eee6-3dd5-55a760d8f4cd@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).