From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context
Date: Wed, 27 Sep 2017 00:20:54 +0200 [thread overview]
Message-ID: <20170926222054.sshmh4t2tson3hyd@pd.tnic> (raw)
In-Reply-To: <BN6PR1201MB01311EC4A9AECE2C99833C49F87B0@BN6PR1201MB0131.namprd12.prod.outlook.com>
On Tue, Sep 26, 2017 at 03:21:22PM +0000, 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 v4.1 and has this issue.
> However, the following commit was included in v4.6 and masks the issue.
>
> b2f9d678e28c x86/mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries
>
> This patch will apply to v4.9 and later. Another version will be needed to apply
> to the v4.1 and v4.4. stable branches.
Then write that in the commit message. But *also* add the main reason
why you're doing this - to explicitly state that IN_KERNEL context is
panicked on on AMD. Because if it weren't for it, old kernels should
simply backport b2f9d678e28c and be done with it.
And I still don't understand the IN_KERNEL_RECOV thing you mention in
the commit message. That's Intel-only, what does it have to do with AMD?
Btw, while at it, fix that signature
static int mce_severity_amd_smca(struct mce *m, int err_ctx)
to
static int mce_severity_amd_smca(struct mce *m, enum context err_ctx)
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-09-26 22:21 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
2017-09-26 15:21 ` Ghannam, Yazen
2017-09-26 22:20 ` Borislav Petkov [this message]
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=20170926222054.sshmh4t2tson3hyd@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®