due to an off-by-one bug in the L1TF patch, the "rare" case of systems still vulnerable is more frequent.
This typically happens on Nehalem+ destop/entry-level server systems with 32G memory installed.
Originally this was reported in OpenSUSE, but I can confirm this is also happens with the latest trusty kernel (3.13.0-157-generic)
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=b0a182f875689647b014bc01d36b340217792852
The following patch increases the memory limit for the mitigation on these systems in general:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4
due to an off-by-one bug in the L1TF patch, the "rare" case of systems still vulnerable
is more frequent.
This typically happens on Nehalem+ destop/entry-level server systems with 32G memory installed.
Originally this was reported in OpenSUSE, but I can confirm this is also happens 157-generic)
with the latest trusty kernel (3.13.0-
https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/tip/ tip.git/ commit/ ?id=b0a182f8756 89647b014bc01d3 6b340217792852
The following patch increases the memory limit for the mitigation on these systems in general:
https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/tip/ tip.git/ commit/ ?h=x86/ urgent& id=cc51e5428ea5 4f575d49cfcede1 d4cb3a72b4ec4