The Meltdown attack requires an attacker to have a piece of code executed on your server. Epic's servers are used for login, where people send you data, and for game logic, where people also just send you data like "player x moved his avatar here, player y shoots etc". If all the server does is execute the code which Epic wrote themselves and already trust, why would it need to apply the Meltdown patch?
CPU Usage Differences After Applying Meltdown Patch at Epic Games
101–110 of 296 posts
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#102Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#103The Meltdown attack requires an attacker to have a piece of code executed on your server. Epic's servers are used for login, where people send you data, and for game logic, where people also just send you data like "player x moved his avatar here, player y shoots etc". If all the server does is execute the code which Epic wrote themselves and already trust, why would it need to apply the Meltdown patch?
This is a horrible approach to security. If you only secure against attacks you expect, you're gonna have a bad time.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#104I know they don't have to share the details, but the "patched" part is not really clear. Did they update to a new image / more recent kernel / anything else? Much like the redis post linked in HN before, we don't know if the impact is because of the "pti turned off/on" change, or are there more moving parts involved.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#105Pretty much what I predicted here: https://news.ycombinator.com/item?id=16054674 > Sounds like servers handling lots of small UDP packets would be hit pretty hard.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#106Edit: It looks like the answer to the first is a definite yes.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#107Earlier quoted context omitted.
It makes sense if you don't want a remote code execution in one of your app to provide a full root shell.
Thank you for the explanation, and especially for being non-snarky, which unfortunately seems to be getting rarer and rarer on this forum.
If this isn't unnecessarily "snarky" itself, then what is it?
snarky: (of a person, words, or a mood) sharply critical; cutting; snide.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#108Maybe off-topic: Is formal verification viable anywhere in CPU logic design? Also, could any existing "CPU static analyzers" have caught the issue that caused Meltdown? Edit: It looks like the answer to the first is a definite yes.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#109The one most interested in is Google versus Amazon.
Re: CPU Usage Differences After Applying Meltdown Patch at Epic Games
#110Maybe off-topic: Is formal verification viable anywhere in CPU logic design? Also, could any existing "CPU static analyzers" have caught the issue that caused Meltdown? Edit: It looks like the answer to the first is a definite yes.
You can only verify properties you've thought of, and no-one conceived of this particular 'feature' causing issues like this until now. So I don't think formal verification would have helped: if anyone was in a position to realise the issue was worth verifying, they'd have been able to raise it without formal verification too.