3 ms·

This seems unnecessary hostile. It's quite obvious that these patches had to be completed in a hurry, and in addition to any number of similar patches for other

This seems unnecessary hostile. It's quite obvious that these patches had to be completed in a hurry, and in addition to any number of similar patches for other systems. Configurability is currently useless for Intel CPUs, as all of them seem to be affected. Depending on how their CPU development pipeline works, it's quite likely that even the next generation will still be affected, giving everyone plenty of time later for such niceties. It's also slightly too harsh to call all of Intel's work "crap" when this bug has apparently existed for the better part of two decades without being noticed.

pricetag 9y ago
>unnecessarily hostile Not that I disagree with you, but are you familiar with Linus’ other uhhh...critiques? http://lkml.iu.edu/hypermail/linux/kernel/1510.3/02866.html http://lkml.iu.edu/hypermail/linux/kernel/1510.3/02866.html
mcny 9y ago
I agree with Linus though. Not that I've ever worked on a big project like the kernel but things like these will take a backburner. The kernel maintainers don't have a way to bring these things up in Intel's boardroom like Apple can and it is possible that Intel will never produce a proper fix.
nkw 9y ago
> had to be completed in a hurry "We reported this issue to Intel, AMD and ARM on 2017-06-01" https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.com/2018/01/reading-privi...
maxlybbert 9y ago
I didn't take the comment as "all Intel CPUs are crap," but that (1) the fix is needed for crap CPUs and (2) the fix is turned on unconditionally on Intel CPUs, even future CPUs. That is, the code itself assumes that all CPUs that could be crap actually are crap. Torvalds wants a flag that could be set appropriately when Intel starts shipping CPUs that don't have this problem.
cryptonector 9y ago
That's Linus. But he's not wrong on this one. If anything he's restrained.

pricetag 9y ago

>unnecessarily hostile Not that I disagree with you, but are you familiar with Linus’ other uhhh...critiques? http://lkml.iu.edu/hypermail/linux/kernel/1510.3/02866.html http://lkml.iu.edu/hypermail/linux/kernel/1510.3/02866.html

mcny 9y ago

I agree with Linus though. Not that I've ever worked on a big project like the kernel but things like these will take a backburner. The kernel maintainers don't have a way to bring these things up in Intel's boardroom like Apple can and it is possible that Intel will never produce a proper fix.

nkw 9y ago

> had to be completed in a hurry "We reported this issue to Intel, AMD and ARM on 2017-06-01" https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.com/2018/01/reading-privi...

maxlybbert 9y ago

I didn't take the comment as "all Intel CPUs are crap," but that (1) the fix is needed for crap CPUs and (2) the fix is turned on unconditionally on Intel CPUs, even future CPUs. That is, the code itself assumes that all CPUs that could be crap actually are crap. Torvalds wants a flag that could be set appropriately when Intel starts shipping CPUs that don't have this problem.

cryptonector 9y ago

That's Linus. But he's not wrong on this one. If anything he's restrained.