Received: by 10.192.165.148 with SMTP id m20csp994984imm; Wed, 2 May 2018 12:11:14 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrd/dQvTkoBAle1EfYc8j+XQ8Uy0Aq3vyVQgVIpLe7wR9r/Hfqk2EgtirTrnzSMNygabQJU X-Received: by 10.98.72.209 with SMTP id q78mr20602585pfi.70.1525288274252; Wed, 02 May 2018 12:11:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525288274; cv=none; d=google.com; s=arc-20160816; b=d/oHNklv1G59IbNel+iUEpXuF6mRu6xsdZTaZy9/xVq6NiU3Tk3YZ+QCJ6QzZTtDFC maHkgsOA6fGuPitl5s7s0Hb8159IWWRzFkeUBAut/rB4eLWZ7mYVeqPOf9a4rsfPcm8r 4e3quSqeBSfSUJg3wv/aGWwywWxoxGn2nt9yDq5WsnCNumQeacxwvJPxL9IIhy5ysXBZ P+ryFiVObSPDakEkNPPTBCpTEMVyN1rU+ozLMSePzYZXFftBUUHynOqnndM+UUueourt eLT4nflVN+8Bbllltfwki8ZzmXoygDtCjhrXBx9CTEnXL8XpTs2kRR4moo6kVFcWFbNY KuFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=ZAGLEKbtJIrkDJEX2/TPv+7xa6fYRvZhT1DgbLwhH+U=; b=FWokmobzplfKmVrUunY0fzUvB/3Im0naklUsYp27OQv9g6TNtS+5oJ4Dy4urFYBR59 BO/bQ+l9d9zKM2ubc/QrN7+FM1zMvk7NjozcLgBuE7yoWArDwy6lFwuSA3VvBxxiYAWy xxH5050EvIXXetCbwdKuuSM4WmV1VPyxbQuouwvZopicXAnU/RnO+D2W4llVl+o+GD3M udXcyeP1T3GxDTnEbI6HPl1BRutT2WZfd322CmPFAviZG75ntxwCzcH0VhxxaffACduy 8nzPqBm4bcw2DFth5fl4fwoVp7/W1SQKDma9yQhwrjfpvTOUwIM8tSzaBnw+dtSBG+7h 6ZwQ== 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 m39-v6si12180400plg.570.2018.05.02.12.11.00; Wed, 02 May 2018 12:11:14 -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 S1751390AbeEBTKe (ORCPT + 99 others); Wed, 2 May 2018 15:10:34 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:50174 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751291AbeEBTKd (ORCPT ); Wed, 2 May 2018 15:10:33 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id A01E1804A3; Wed, 2 May 2018 21:10:31 +0200 (CEST) Date: Wed, 2 May 2018 21:10:30 +0200 From: Pavel Machek To: Borislav Petkov Cc: Alexandru Gagniuc , linux-acpi@vger.kernel.org, linux-edac@vger.kernel.org, "Rafael J. Wysocki" , Len Brown , Tony Luck , Mauro Carvalho Chehab , Robert Moore , Erik Schmauss , Tyler Baicar , Will Deacon , James Morse , Shiju Jose , "Jonathan (Zhixiong) Zhang" , Dongjiu Geng , linux-kernel@vger.kernel.org, devel@acpica.org Subject: Re: [RFC PATCH v3 3/3] acpi: apei: Warn when GHES marks correctable errors as "fatal" Message-ID: <20180502191029.hcvf56xbdna7oi4k@devuan> References: <20180416215903.7318-1-mr.nuke.me@gmail.com> <20180425203957.18224-1-mr.nuke.me@gmail.com> <20180425203957.18224-4-mr.nuke.me@gmail.com> <20180426112057.GB15009@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180426112057.GB15009@pd.tnic> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2018-04-26 13:20:57, Borislav Petkov wrote: > On Wed, Apr 25, 2018 at 03:39:51PM -0500, Alexandru Gagniuc wrote: > > There seems to be a culture amongst BIOS teams to want to crash the > > OS when an error can't be handled in firmware. Marking GHES errors as > > "fatal" is a very common way to do this. > > > > However, a number of errors reported by GHES may be fatal in the sense > > a device or link is lost, but are not fatal to the system. When there > > is a disagreement with firmware about the handleability of an error, > > print a warning message. > > + > > + if ((sev >= GHES_SEV_PANIC) && (ghes_actual_severity(ghes) < sev)) { > > + pr_warn("FIRMWARE BUG: Firmware sent fatal error that we were able to correct"); > > + pr_warn("BROKEN FIRMWARE: Complain to your hardware vendor"); > > Pasting the same comment from last time since you missed it: > > "No, I don't want any of that crap issuing stuff in dmesg and then people > opening bugs and running around and trying to replace hardware. We want to see warnings. Maybe they can be toned done. We even have dedicated distros for firmware testing. > Good mailing practices for 400: avoid top-posting and trim the reply. Good mailing practices -- limit use of four letter words on public lists. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html