lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <4B17393B.7000304@majjas.com>
Date:	Wed, 02 Dec 2009 23:06:19 -0500
From:	Michael Breuer <mbreuer@...jas.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Bug (minor): microcode_intel.c applies updates to hyperthreaded cores

According to spec, microcode should only be applied to actual cores. As
things are currently structured, looks like the fix would be in
microcode_core.c. I don't think changing the loop to look for cores vs.
cpu's would affect anything adversely, but honestly am not familiar
enough with this code or other cpu types to be sure.

As far as I can tell, the only adverse impact of this issue is boot
performance in the event that microcode is applied to a large number of
processors in a hyper-threaded environment. I've only got one chip, so
no real issues here. Just happened to notice.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ