mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Yazen Ghannam <Yazen.Ghannam@amd.com>
Cc: linux-edac@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context
Date: Tue, 26 Sep 2017 14:01:15 +0200	[thread overview]
Message-ID: <20170926120115.z7rorwli3idaxxyr@pd.tnic> (raw)
In-Reply-To: <1505830031-9630-1-git-send-email-Yazen.Ghannam@amd.com>

(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 <yazen.ghannam@amd.com>
> 
> 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.

  reply	other threads:[~2017-09-26 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 14:07 Yazen Ghannam
2017-09-26 12:01 ` Borislav Petkov [this message]
2017-09-26 15:21   ` Ghannam, Yazen
2017-09-26 22:20     ` Borislav Petkov
2017-09-27 15:17       ` Ghannam, Yazen
2017-09-27 15:26         ` Borislav Petkov
2017-11-21 15:05 [PATCH] x86/MCE/AMD: Always give panic " Yazen Ghannam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170926120115.z7rorwli3idaxxyr@pd.tnic \
    --to=bp@alien8.de \
    --cc=Yazen.Ghannam@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®