From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030562AbdIZMB1 (ORCPT ); Tue, 26 Sep 2017 08:01:27 -0400 Received: from mail.skyhub.de ([5.9.137.197]:41332 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030531AbdIZMBZ (ORCPT ); Tue, 26 Sep 2017 08:01:25 -0400 Date: Tue, 26 Sep 2017 14:01:15 +0200 From: Borislav Petkov To: Yazen Ghannam Cc: linux-edac@vger.kernel.org, Tony Luck , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context Message-ID: <20170926120115.z7rorwli3idaxxyr@pd.tnic> References: <1505830031-9630-1-git-send-email-Yazen.Ghannam@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1505830031-9630-1-git-send-email-Yazen.Ghannam@amd.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (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. The current #MC handler only calls > memory_failure() on errors in user context, but older versions will call > memory_failure() unconditionally. Err, I don't understand this aspect: what does "older versions" mean here exactly? There are no older versions of the #MC handler - there's only one version - the version against which this patch gets applied. Hmmm? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.