Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp2983191imm; Sun, 1 Jul 2018 09:40:26 -0700 (PDT) X-Google-Smtp-Source: AAOMgpflqyDuVSgS6p2JVuEDuXrD71+9eYDu+xGytzRQ1NrG5MBPEr6RYZJmeTHXfF9QkJj/J4N+ X-Received: by 2002:aa7:81d3:: with SMTP id c19-v6mr22258243pfn.224.1530463226768; Sun, 01 Jul 2018 09:40:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530463226; cv=none; d=google.com; s=arc-20160816; b=cjESSGR7nNHmgeElENtrCqIPMjBi8RUs2HyP2NlR7TXIWJMJCojP8iWa6X6YieKVWz HB9NUs2HnHNhGFGrbNOno1k7hLBZToZSmXaSABqEH3371d0Vx3x147D6LraUOnd8YRhX cehJ9Ek8uazXoRtfhbFke3qslsWZAP4wl6E/Xd/TGx/bX4ka5oc4U2S0iuGZJNGIhD58 GinOcQvskj3oN3HOlWmXVyPKh4tdiaMUBBi+pCzfl/6Q9WYZxxjlIjdcviDN1w0Lo7Cz h+zcFp9e5BCxVyTY4++dgV5QbKK/9NSa/E7PLZyhJfthXht1XQuUmkE9VeKf76vX8IuS G82w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=BB24Gex4Ir/B5dQBZRieL5PsaMwQHjNDNTG9vsWhXlQ=; b=tgrojhZS0F4GWFac2TBs45XhpBmTKE1GhN9JwLdOyDmN6LXg1JGANd4u1hpiY0x7Rq LTrdLOa1m8hh7P9nNyg3ny22E9uw6JrWDsEmrI38FKMit7hyYih1hnwW5nW6pzbdpXXC OHHVcWxv5HEBuCtDt/dGTUeX6rhquf4gHMKdgBnxaUmVG7xJiS2ZACLg0/Y0g+kAy1DT tgK1jfl0o5tpdjHWzx3+60FATEPWPRB764bomTE6M/jQqqY+llTSRmGnABweCp90jM07 F8HvVosmbTkSHqIqI+mr13g8aXEhV5nQEL83fV4+OiILakWNL6QNXeGLSj3LFiU5J98l ji0A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t1-v6si13647450plo.241.2018.07.01.09.40.12; Sun, 01 Jul 2018 09:40:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031568AbeGAQiP (ORCPT + 99 others); Sun, 1 Jul 2018 12:38:15 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:36638 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031539AbeGAQiG (ORCPT ); Sun, 1 Jul 2018 12:38:06 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 4A428ACD; Sun, 1 Jul 2018 16:38:05 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Tony Luck , Thomas Gleixner , Qiuxu Zhuo , Ashok Raj , Dan Williams , Borislav Petkov Subject: [PATCH 4.17 006/220] x86/mce: Improve error message when kernel cannot recover Date: Sun, 1 Jul 2018 18:20:30 +0200 Message-Id: <20180701160908.562327665@linuxfoundation.org> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20180701160908.272447118@linuxfoundation.org> References: <20180701160908.272447118@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.17-stable review patch. If anyone has any objections, please let me know. ------------------ From: Tony Luck commit c7d606f560e4c698884697fef503e4abacdd8c25 upstream. Since we added support to add recovery from some errors inside the kernel in: commit b2f9d678e28c ("x86/mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries") we have done a less than stellar job at reporting the cause of recoverable machine checks that occur in other parts of the kernel. The user just gets the unhelpful message: mce: [Hardware Error]: Machine check: Action required: unknown MCACOD doubly unhelpful when they check the manual for the reported IA32_MSR_STATUS.MCACOD and see that it is listed as one of the standard recoverable values. Add an extra rule to the MCE severity table to catch this case and report it as: mce: [Hardware Error]: Machine check: Data load in unrecoverable area of kernel Fixes: b2f9d678e28c ("x86/mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries") Signed-off-by: Tony Luck Signed-off-by: Thomas Gleixner Cc: Qiuxu Zhuo Cc: Ashok Raj Cc: stable@vger.kernel.org # 4.6+ Cc: Dan Williams Cc: Borislav Petkov Link: https://lkml.kernel.org/r/4cc7c465150a9a48b8b9f45d0b840278e77eb9b5.1527283897.git.tony.luck@intel.com Signed-off-by: Greg Kroah-Hartman --- arch/x86/kernel/cpu/mcheck/mce-severity.c | 5 +++++ 1 file changed, 5 insertions(+) --- a/arch/x86/kernel/cpu/mcheck/mce-severity.c +++ b/arch/x86/kernel/cpu/mcheck/mce-severity.c @@ -160,6 +160,11 @@ static struct severity { SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR|MCACOD, MCI_UC_SAR|MCI_ADDR|MCACOD_INSTR), USER ), + MCESEV( + PANIC, "Data load in unrecoverable area of kernel", + SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR|MCACOD, MCI_UC_SAR|MCI_ADDR|MCACOD_DATA), + KERNEL + ), #endif MCESEV( PANIC, "Action required: unknown MCACOD",