3 ms·
Well Intel for one manufactures the insecure CPUs.. This will be merged for 4.16, when there is no 4.15 release yet. No idea what your cloud computing companie
by revelation 9y ago
Well Intel for one manufactures the insecure CPUs..
This will be merged for 4.16, when there is no 4.15 release yet. No idea what your cloud computing companies run but it's not 4.15-dirty, and backporting this monster is a great recipe for a nightly emergency when it goes OOPS.
edit: it isn't even merged yet.
- justincormack 9y agoIt is being backported to 4.14, and presumably earlier kernel too.
- revelation 9y agoSure, with the appropriate baking time. But I don't see a cloud company taking an intermediate version of this patchset, backporting it themselves and then sending it out to all their customers in a hurry.
- tonfa 9y agoWhy not? Isn't that what they should do in case of a kernel security issue?
- cookiecaper 9y agoYep. The kernel maintainers are being so aggressive with this that I'll be very concerned if there isn't a major security issue coming down the pipe. I know that Linux is considered fast and loose in various circles of old-school hackers, and granted, but merging this type of fundamental change into stable is not normal. There's something brewing here that is pushing this to completion.
- amluto 9y agoLike the backports here? https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux... Go test! I agree, they're very scary. Also, watch out: a kernel with PTI on will not function in KVM-emulated secure boot mode until a KVM fix gets backported as well.
- mackal 9y agoSome of these patches are already on stable marked kernels. In fact, I'm already running them. There was also an issue where some different default GCC flags hardened gentoo uses was causing the kernel to not be able to boot.