Jest ktoś z was dotknięty przez spectre/meltdown w pracy? jak to naprawdę wygląda?

Cześć, może to pytanie bardziej do sysadminów niż programistów, ale może ktoś coś?

Czy widać duży drop wydajności na vmkach? (bo na zwykłym pc nie ma różnicy, lub jest marginalna)

• Jeżeli tak, to jakie są możliwe rozwiązania na dłuższą metę? więcej maszyn? znacznie lepsze procki? przejście na AMD aby uniknąć Meltdowna?

Bardziej panika, czy jednak ludzie odpowiedzialni za infrastrukturę raczej ogarniają sprawę?

Tutaj macie chyba wszystko na ten temat (na dole nawet są linki do postów np. od amd/intela/googla itd) https://meltdownattack.com/

Exploiting Speculative Execution via Javascript" is possibly one of the most terrifying lines of text I've ever seen, especially since this implies DUMPING KERNEL MEMORY from JAVASCRIPT

@Gynvael Coldwind huh?

lol

From	Linus Torvalds <>
Date	Wed, 3 Jan 2018 15:51:35 -0800
Subject	Re: Avoid speculative indirect calls in kernel

Why is this all done without any configuration options?

A *competent* CPU engineer would fix this by making sure speculation
doesn't happen across protection domains. Maybe even a L1 I$ that is
keyed by CPL.

I think somebody inside of Intel needs to really take a long hard look
at their CPU's, and actually admit that they have issues instead of
writing PR blurbs that say that everything works as designed.

.. and that really means that all these mitigation patches should be
written with "not all CPU's are crap" in mind.

Or is Intel basically saying "we are committed to selling you shit
forever and ever, and never fixing anything"?

Because if that's the case, maybe we should start looking towards the
ARM64 people more.

Please talk to management. Because I really see exactly two possibibilities:

 - Intel never intends to fix anything

OR

 - these workarounds should have a way to disable them.

Which of the two is it?

https://lkml.org/lkml/2018/1/3/797