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
| ||
|
Date: Thu, 6 Feb 2020 08:05:24 -0500 From: Prarit Bhargava <prarit@...hat.com> To: Borislav Petkov <bp@...en8.de> Cc: linux-kernel@...r.kernel.org, Alexander Krupp <centos@....yagii.de>, Tony Luck <tony.luck@...el.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org, linux-edac@...r.kernel.org Subject: Re: [PATCH] x86/mce: Enable HSD131, HSM142, HSW131, BDM48, and HSM142 On 2/6/20 7:53 AM, Prarit Bhargava wrote: > > > On 2/6/20 6:10 AM, Borislav Petkov wrote: >> On Wed, Feb 05, 2020 at 07:58:31AM -0500, Prarit Bhargava wrote: >> >>> Subject: Re: [PATCH] x86/mce: Enable HSD131, HSM142, HSW131, BDM48, and HSM142 >> >> That subject is unreadable for humans. > > Yeah :/ I couldn't think of a better one. Maybe "Block spurious corrected > errors on some Intel processors"? Any other suggestion? > >> >>> Intel Errata HSD131, HSM142, HSW131, and BDM48 report that >>> "spurious corrected errors may be logged in the IA32_MC0_STATUS register >>> with the valid field (bit 63) set, the uncorrected error field (bit 61) >>> not set, a Model Specific Error Code (bits [31:16]) of 0x000F, and >>> an MCA Error Code (bits [15:0]) of 0x0005." >>> >>> Block these spurious errors from the console and logs. >> >> Are they being hit in the wild or why do we need this? > > Alexander, cc'd, is being hit by this in the wild. > >> >>> Links to Intel Specification updates: >>> HSD131: https://www.intel.com/content/www/us/en/products/docs/processors/core/4th-gen-core-family-desktop-specification-update.html >>> HSM142: https://www.intel.com/content/www/us/en/products/docs/processors/core/4th-gen-core-family-mobile-specification-update.html >>> HSW131: https://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200v3-spec-update.html >>> BDM48: https://www.intel.com/content/www/us/en/products/docs/processors/core/5th-gen-core-family-spec-update.html >> >> Those links tend to get stale with time. If you really want to refer to >> the PDFs, add a new bugzilla entry on https://bugzilla.kernel.org/, add >> them there as an attachment and add the link to the entry to the commit >> message. >> >>> Signed-off-by: Alexander Krupp <centos@....yagii.de> >> >> What's that Signed-off-by: tag supposed to mean? Sorry. I missed this question, but I really don't understand the question. Alexander posted a patch in a kernel bugzilla @ Red Hat and I modified the patch with some additional changes. I don't want him to lose credit for the work so he's got a proper Signed-off-by tag for this patch. P.
Powered by blists - more mailing lists