diff options
author | Borislav Petkov <borislav.petkov@amd.com> | 2012-06-21 12:07:16 (GMT) |
---|---|---|
committer | H. Peter Anvin <hpa@zytor.com> | 2012-07-01 17:24:05 (GMT) |
commit | c9fc3f778a6a215ace14ee556067c73982b6d40f (patch) | |
tree | 588ddfd51b9b2806c5ace340d44f54d144ef8128 /include/trace | |
parent | 6887a4131da3adaab011613776d865f4bcfb5678 (diff) | |
download | linux-c9fc3f778a6a215ace14ee556067c73982b6d40f.tar.xz |
x86, microcode: Sanitize per-cpu microcode reloading interface
Microcode reloading in a per-core manner is a very bad idea for both
major x86 vendors. And the thing is, we have such interface with which
we can end up with different microcode versions applied on different
cores of an otherwise homogeneous wrt (family,model,stepping) system.
So turn off the possibility of doing that per core and allow it only
system-wide.
This is a minimal fix which we'd like to see in stable too thus the
more-or-less arbitrary decision to allow system-wide reloading only on
the BSP:
$ echo 1 > /sys/devices/system/cpu/cpu0/microcode/reload
...
and disable the interface on the other cores:
$ echo 1 > /sys/devices/system/cpu/cpu23/microcode/reload
-bash: echo: write error: Invalid argument
Also, allowing the reload only from one CPU (the BSP in
that case) doesn't allow the reload procedure to degenerate
into an O(n^2) deal when triggering reloads from all
/sys/devices/system/cpu/cpuX/microcode/reload sysfs nodes
simultaneously.
A more generic fix will follow.
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
Link: http://lkml.kernel.org/r/1340280437-7718-2-git-send-email-bp@amd64.org
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Cc: <stable@vger.kernel.org>
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions