summaryrefslogtreecommitdiff
path: root/security/inode.c
diff options
context:
space:
mode:
authorBorislav Petkov <borislav.petkov@amd.com>2010-10-08 10:08:34 (GMT)
committerIngo Molnar <mingo@elte.hu>2010-10-11 09:04:36 (GMT)
commit6dcbfe4f0b4e17e289d56fa534b7ce5a6b7f63a3 (patch)
tree2fa24b374dd8062cbd8039a170ca3721b69e655f /security/inode.c
parentb62be8ea9db4048112219ff6d6ce5f183179d4dc (diff)
downloadlinux-fsl-qoriq-6dcbfe4f0b4e17e289d56fa534b7ce5a6b7f63a3.tar.xz
x86, AMD, MCE thresholding: Fix the MCi_MISCj iteration order
This fixes possible cases of not collecting valid error info in the MCE error thresholding groups on F10h hardware. The current code contains a subtle problem of checking only the Valid bit of MSR0000_0413 (which is MC4_MISC0 - DRAM thresholding group) in its first iteration and breaking out if the bit is cleared. But (!), this MSR contains an offset value, BlkPtr[31:24], which points to the remaining MSRs in this thresholding group which might contain valid information too. But if we bail out only after we checked the valid bit in the first MSR and not the block pointer too, we miss that other information. The thing is, MC4_MISC0[BlkPtr] is not predicated on MCi_STATUS[MiscV] or MC4_MISC0[Valid] and should be checked prior to iterating over the MCI_MISCj thresholding group, irrespective of the MC4_MISC0[Valid] setting. Signed-off-by: Borislav Petkov <borislav.petkov@amd.com> Cc: <stable@kernel.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'security/inode.c')
0 files changed, 0 insertions, 0 deletions