summaryrefslogtreecommitdiff
path: root/include/linux/edac.h
diff options
context:
space:
mode:
authorRui Wang <ruiv.wang@gmail.com>2013-12-08 08:17:53 +0400
committerBorislav Petkov <bp@suse.de>2013-12-08 18:39:10 +0400
commit545104dd2ba0feb62544284ee1d6c98fe6ef8245 (patch)
treee785653c7c11a37048dccb0e0f70fa57a5687580 /include/linux/edac.h
parent853d9b18f1e861d37e9b271742329f8c1176eabe (diff)
downloadlinux-545104dd2ba0feb62544284ee1d6c98fe6ef8245.tar.xz
PCI, AER: Fix severity usage in aer trace event
There's inconsistency between dmesg and the trace event output. When dmesg says "severity=Corrected", the trace event says "severity=Fatal". What happens is that HW_EVENT_ERR_CORRECTED is defined in edac.h: enum hw_event_mc_err_type { HW_EVENT_ERR_CORRECTED, HW_EVENT_ERR_UNCORRECTED, HW_EVENT_ERR_FATAL, HW_EVENT_ERR_INFO, }; while aer_print_error() uses aer_error_severity_string[] defined as: static const char *aer_error_severity_string[] = { "Uncorrected (Non-Fatal)", "Uncorrected (Fatal)", "Corrected" }; In this case dmesg is correct because info->severity is assigned in aer_isr_one_error() using the definitions in include/linux/ras.h: Signed-off-by: Rui Wang <rui.y.wang@intel.com> Acked-by: Ethan Zhao <ethan.kernel@gmail.com> Link: http://lkml.kernel.org/r/CANVTcTaP18CiGOSEcX5Ch_wPw9mEhkgokfp+d+ZOMFD+Ce4juA@mail.gmail.com Signed-off-by: Borislav Petkov <bp@suse.de>
Diffstat (limited to 'include/linux/edac.h')
0 files changed, 0 insertions, 0 deletions