Earlier quoted context omitted.
Within the CPU core (terminology here gets awkward). Spectre in its simplest to exploit form used the fact that the branch prediction based state wasn't completely cleared between running different threads on the CPU and led to a really easy timing attack. Time your own code to see which way the branch of the previous code likely went. There's a lot of CVE's around this but that's the simplest case. The mitigations w…
Is it likely the issue is within the Linux kernel itself or within the microcode for the CPU?
Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
31–40 of 47 posts
Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#32Isn't there a rule about titles containing 'considered harmful'? Either way, this is pretty interesting and the guy is pretty excited about finding it.
There is a rule on mostly not editorializing titles and in this case that is the title of the source article. > Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.
Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#33edit: looks like it dies in this: https://github.com/gcc-mirror/gcc/blob/master/gcc/tree-switc...
edit2: it also would've been nice to see the actual bytes being decoded when it faults, maybe it ends up spuriously writing over .text
edit3: on the LKML https://lore.kernel.org/lkml/D99589F4-BC5D-430B-87B2-72C2037...
Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#34Earlier quoted context omitted.
Is it likely the issue is within the Linux kernel itself or within the microcode for the CPU?
I'm going to say microcode until someone reproduces on a completely different architecture :).
Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#35Interesting walk through in the linked video as he tried to troubleshoot this: https://www.youtube.com/live/1UnoBfw6soI Pretty shocking to see (extremely unlikely) non-malicious code work / not-work depending on a security mitigation setting. Curious to see where this goes as to whether it's a kernel bug and nobody is paying attention to `mitigations=off` now or the unlikely outcome that it's an actual hardware bug w…
What does he say at 8:17?[1] Arsink Overism? [1]: https://www.youtube.com/live/1UnoBfw6soI?si=R8nJ1FxdE4zBuO0i...
Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#36Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#37Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#38Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#39Re: Mitigations=off considered harmful or spurious SIGILL on AMD Zen4
#40Interesting walk through in the linked video as he tried to troubleshoot this: https://www.youtube.com/live/1UnoBfw6soI Pretty shocking to see (extremely unlikely) non-malicious code work / not-work depending on a security mitigation setting. Curious to see where this goes as to whether it's a kernel bug and nobody is paying attention to `mitigations=off` now or the unlikely outcome that it's an actual hardware bug w…
Mitigations can have very large effects on system stability, I ran into this with my old Haswell system. Mitigations on allowed, I believe, 100Mhz higher at lower voltage - but it may have been 200Mhz. These settings were tested over many months, completely stable, and mitigations off with the same setting wouldn't even allow booting. Huge effect relative to anything else, basically like adding an extra 0.1V vcore.