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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210401181854.GB11782@zn.tnic>
Date:   Thu, 1 Apr 2021 20:18:54 +0200
From:   Borislav Petkov <bp@...e.de>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     tony.luck@...el.com, linux-kernel@...r.kernel.org, riel@...riel.com
Subject: Re: Backporting to v5.6: fd258dc4442c ("x86/mce: Add Skylake quirk
 for patrol scrub reported errors")

Hey Paul,

On Thu, Apr 01, 2021 at 09:17:40AM -0700, Paul E. McKenney wrote:
> Hello!
> 
> We are looking at backporting fd258dc4442c ("x86/mce: Add Skylake quirk
> for patrol scrub reported errors") to v5.6.  When accompanied by these
> guys, it passes our usual kernel smoke-testing:
> 
> 1df73b2131e3 ("x86/mce: Fixup exception only for the correct MCEs")
> 1de08dccd383 ("x86/mce: Add a struct mce.kflags field")

why do you even need those two?

fd258dc4442c gives you only an Action Optional severity for that
particular error type and the other two patches are for recovery of
errors in the kernel memory range, i.e., for pmem etc., so should be
unrelated.

I mean, it depends on what you want to backport, ofc.

HTH.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ