From: Julia Lawall <julia.lawall@lip6.fr>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Xavier Leroy <xavier.leroy@inria.fr>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] [IMPORTANT] Intel Skylake / Kaby Lake hardware bug affects OCaml programs
Date: Fri, 30 Jun 2017 10:30:57 -0600 (MDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1706301029030.3077@hadrien> (raw)
In-Reply-To: <CAPFanBEwTMtfoKcBy9bNgdjC7u81wGn+ehBLiwaU7fRtg_oi8A@mail.gmail.com>
On Fri, 30 Jun 2017, Gabriel Scherer wrote:
> Here is my list of affected OCaml projects known so far (it seems
> surprisingly less rare than I thought at first):
>
> - an (unnamed) industrial user noticed the issue in Spring 2016, as
> reported by Xavier on the bugtracker:
> https://caml.inria.fr/mantis/view.php?id=7452#c17109
>
> - ahrefs noticed issues in late 2016, as reported by Joris
> Giovannangeli on the bugtracker issue or his longer piece
> https://tech.ahrefs.com/skylake-bug-a-detective-story-ab1ad2beddcd
>
> - Lwt users were also affected (first report from Sebastien Mondet in
> February 2017):
> https://github.com/ocsigen/lwt/issues/315
>
> - Julia Lawall reported segfaults from a downstream user on the caml-list,
> that seem extreley likely to be related to this issue (they
> disappear with hyperthreading disabled)
> https://sympa.inria.fr/sympa/arc/caml-list/2017-06/msg00115.html
>
> At this point it seems reasonable to assume that any
> computation-intensive OCaml program that is run in parallel may be
> affected.
The Coccinelle code is compiled with Parmap, but I don't think that Parmap
is invoked in the failing execution. I could check on this.
julia
>
> On Fri, Jun 30, 2017 at 10:15 AM, Xavier Leroy <xavier.leroy@inria.fr> wrote:
> > Clarification:
> >
> >> Possible fixes include:
> >>
> >> - Apply the microcode update recently released by Intel [...]
> >
> > Contradicting what I wrote before, microcode updates are available both for Skylake and for Kaby Lake processors. It's only how to apply those updates that differs slightly between Skylake and Kaby Lake. Again, see the excellent instructions at
> > https://lists.debian.org/debian-devel/2017/06/msg00308.html
> >
> > Sorry for the confusion.
> >
> > - Xavier Leroy
> >
> > --
> > Caml-list mailing list. Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2017-06-30 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:51 Xavier Leroy
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 [this message]
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=alpine.DEB.2.20.1706301029030.3077@hadrien \
--to=julia.lawall@lip6.fr \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=xavier.leroy@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).