News for hackers. Stuff that matters.
Re:Microsoft disables Spectre mitigations as Intel’s patches... by cm2187 on Monday January 29, 2018 @04:01AM (#16256298)
I thought he was angry about the mitigation being disabled by default, not being unstable.
Re:Microsoft disables Spectre mitigations as Intel’s patches... by icebraining on Monday January 29, 2018 @04:29AM (#16256411)
Nah, it was more than that: The patches do things like add the garbage MSR writes to the kernel entry/exit points. That's insane. That says "we're trying to protect the kernel". We already have retpoline there, with less overhead.
Re:Microsoft disables Spectre mitigations as Intel’s patches... by rocqua on Monday January 29, 2018 @04:45AM (#16256478)
That was about patches to the linux kernel, not the microcode patches.
Re:Microsoft disables Spectre mitigations as Intel’s patches... by icebraining on Monday January 29, 2018 @04:52AM (#16256509)
Yes, but as far as I know Linus has made no comment on the microcode patches, so mm-vorticesoft is probably referring to the Spectre patches in general.
Re:Microsoft disables Spectre mitigations as Intel’s patches... by jononor on Monday January 29, 2018 @07:54AM (#16257182)
The microcode patches are binary blobs against a proprietary and secret ISA, how can anyone comment on their quality?
Re:Microsoft disables Spectre mitigations as Intel’s patches... by mjevans on Monday January 29, 2018 @05:54PM (#16261357)
When I read it I believed that Linus was implying that the suggested mitigation was so insane that it seemed like Intel MIGHT be hiding how broken they believed their hardware was with such over-the-top reactions. As well as indirectly asking if they believed the currently accepted mitigation method (retpoline) was considered ineffective.
Re:Microsoft disables Spectre mitigations as Intel’s patches... by sundarurfriend on Monday January 29, 2018 @08:45AM (#16257421)
His overall point was a bewilderment at the incompetent and non-sensical patches that were being given as "fixes" in this issue. Linus was pointing out a particular instance of that, but this news and other behaviour from Intel seems to indicate this is part of an endemic, cultural, administrative issue inside the company.