[PATCH] x86/MCE/AMD: Always give panic severity for UC errors in kernel context

2017-11-21 Thread Yazen Ghannam
From: Yazen Ghannam [Upstream commit d65dfc81bb3894fdb68cbc74bbf5fb48d2354071] The AMD severity grading function was introduced in kernel 4.1. The current logic can possibly give MCE_AR_SEVERITY for uncorrectable errors in kernel context. The system may then get stuck in

[PATCH] x86/MCE/AMD: Always give panic severity for UC errors in kernel context

2017-11-21 Thread Yazen Ghannam
From: Yazen Ghannam [Upstream commit d65dfc81bb3894fdb68cbc74bbf5fb48d2354071] The AMD severity grading function was introduced in kernel 4.1. The current logic can possibly give MCE_AR_SEVERITY for uncorrectable errors in kernel context. The system may then get stuck in a loop as

Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-27 Thread Borislav Petkov
On Wed, Sep 27, 2017 at 03:17:51PM +, Ghannam, Yazen wrote: > Generally, we can use the IN_KERNEL_RECOV context to show that the error > is recoverable versus IN_KERNEL which we can consider unrecoverable. > > Specifically, the Intel SER and AMD SUCCOR features represent the same > thing (MCA

Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-27 Thread Borislav Petkov
On Wed, Sep 27, 2017 at 03:17:51PM +, Ghannam, Yazen wrote: > Generally, we can use the IN_KERNEL_RECOV context to show that the error > is recoverable versus IN_KERNEL which we can consider unrecoverable. > > Specifically, the Intel SER and AMD SUCCOR features represent the same > thing (MCA

RE: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-27 Thread Ghannam, Yazen
> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Tuesday, September 26, 2017 6:21 PM > To: Ghannam, Yazen ... > > There are the stable branches on kernel.org and some distro kernels > > based on older kernel versions. > > > > The AMD

RE: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-27 Thread Ghannam, Yazen
> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Tuesday, September 26, 2017 6:21 PM > To: Ghannam, Yazen ... > > There are the stable branches on kernel.org and some distro kernels > > based on older kernel versions. > > > > The AMD severity grading function

Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-26 Thread Borislav Petkov
On Tue, Sep 26, 2017 at 03:21:22PM +, Ghannam, Yazen wrote: > How should I CC:stable? Documentation/process/stable-kernel-rules.rst > There are the stable branches on kernel.org and some distro kernels based on > older kernel versions. > > The AMD severity grading function was introduced in

Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-26 Thread Borislav Petkov
On Tue, Sep 26, 2017 at 03:21:22PM +, Ghannam, Yazen wrote: > How should I CC:stable? Documentation/process/stable-kernel-rules.rst > There are the stable branches on kernel.org and some distro kernels based on > older kernel versions. > > The AMD severity grading function was introduced in

RE: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-26 Thread Ghannam, Yazen
@vger.kernel.org > Subject: Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC > errors in kernel context > > (drop CC:stable from CC list) > > Do not add CC:stable when sending the patch with git send-email. > How should I CC:stable? > On Tue, Sep 19, 2017 at

RE: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-26 Thread Ghannam, Yazen
> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Tuesday, September 26, 2017 8:01 AM > To: Ghannam, Yazen > Cc: linux-e...@vger.kernel.org; Tony Luck ; > x...@kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] x86/MCE/A

Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-26 Thread Borislav Petkov
(drop CC:stable from CC list) Do not add CC:stable when sending the patch with git send-email. On Tue, Sep 19, 2017 at 09:07:11AM -0500, Yazen Ghannam wrote: > From: Yazen Ghannam > > Our current AMD severity logic can possibly give MCE_AR_SEVERITY for > uncorrectable

Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-26 Thread Borislav Petkov
(drop CC:stable from CC list) Do not add CC:stable when sending the patch with git send-email. On Tue, Sep 19, 2017 at 09:07:11AM -0500, Yazen Ghannam wrote: > From: Yazen Ghannam > > Our current AMD severity logic can possibly give MCE_AR_SEVERITY for > uncorrectable errors in kernel context.

[PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-19 Thread Yazen Ghannam
From: Yazen Ghannam Our current AMD severity logic can possibly give MCE_AR_SEVERITY for uncorrectable errors in kernel context. The current #MC handler only calls memory_failure() on errors in user context, but older versions will call memory_failure() unconditionally. In

[PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context

2017-09-19 Thread Yazen Ghannam
From: Yazen Ghannam Our current AMD severity logic can possibly give MCE_AR_SEVERITY for uncorrectable errors in kernel context. The current #MC handler only calls memory_failure() on errors in user context, but older versions will call memory_failure() unconditionally. In older versions, the