Comments on: CPU bug hardening added to DragonFly

By: Justin Sherrill

Justin Sherrill — Thu, 21 Jun 2018 04:09:18 +0000

There’s sysctls that control the behavior for this and other vulnerabilities, so they are already optional. They are described in the commit messages.

By: Eric Olson

Eric Olson — Thu, 21 Jun 2018 03:39:17 +0000

There are starting to be lots of defensive measures being taken to prevent information leakage through side-channels resulting from speculative execution which appear computationally expensive. While desktop usage and certain kinds of server and cloud usage benefit from these mitigations, there are other cases, for example high performance computing, where one doesn’t care about information leakage through side-channels created by speculative execution. Any thoughts on making all performance compromising mitigations optional?

By: Freddie

Freddie — Thu, 14 Jun 2018 15:30:32 +0000

http://undeadly.org/cgi?action=article;sid=20180614064341

There’s a brief blurb about it on undeadly as well.

By: Justin Sherrill

Justin Sherrill — Tue, 12 Jun 2018 17:54:37 +0000

Thank you for finding that.

By: CB

CB — Tue, 12 Jun 2018 17:15:09 +0000

Here’s the commit message from OpenBSD: https://marc.info/?l=openbsd-cvs&m=152818076013158&w=2

Diff: https://github.com/openbsd/src/commit/c9de630f2b8eca49826c5a19f6e33a38c26295b2 (on github because cvsweb doesn’t show changesets)