Thanks for the clarification. Is there any reason for this bug to remain private? It is well known that "nosmt" is needed to mitigate CPU side channel issues, such as CVE-2018-3646, and sufficiently paranoid folks have been using it quite a bit lately.
Thanks for the clarification. Is there any reason for this bug to remain private? It is well known that "nosmt" is needed to mitigate CPU side channel issues, such as CVE-2018-3646, and sufficiently paranoid folks have been using it quite a bit lately.