From: Borislav Petkov <bp@alien8.de>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Guixiong Wei <weiguixiong@bytedance.com>,
Tony Luck <tony.luck@intel.com>,
Muralidhara M K <muralidhara.mk@amd.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] EDAC/mce_amd: Add missing long names for SMCA bank types
Date: Sun, 18 Oct 2026 16:07:51 -0700 [thread overview]
Message-ID: <20261018230751.GBatVRR1NLJCBJrLIB@fat_crate.local> (raw)
In-Reply-To: <20261018223431.GA3236@yaz-khff2.amd.com>
On Sun, Oct 18, 2026 at 06:34:31PM -0400, Yazen Ghannam wrote:
> "a" is better.
Nope.
Typing raw error values from a screen because the machine died and there's no
serial, or making a screen cap and then OCRing it and then finding another
machine to decode it on after checking the OCR did read the hex values
properly and yadda yadda...
vs
simply reading the properly decoded error decode from the screen is not
better, no matter from where you look at it.
> The same "is not updated with the latest error definitions" applies to
> the kernel.
You probably mean distro kernels. Because we try to have those updates
mainline as fast as possible.
> And it's usually easier to update tools than patch the kernel (and also
> deal with backporting, etc.).
Yah, backporting kernels has a lag in it but if the decoding updates are
upstream, distros do tend to pick them up.
> In any case, this patch isn't about error descriptions. It's only about
> adding the names for some bank types.
>
> The bank types were added three years ago. AFAIK, the missing names
> haven't been an issue. So I'm curious if this patch is actually fixing a
> problem. If so, then that's fine.
We dump the smca_long_names:
pr_emerg(HW_ERR "%s Ext. Error Code: %d", smca_get_long_name(bank_type), xec);
On that patch I objected to the Cc: <stable@kernel.org> marker but if distro
kernels are the problem wrt decoding MCEs, we can change that and simply route
all *purely* decoding patches to stable.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-10-18 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 2:04 Guixiong Wei
2026-10-09 5:07 ` Borislav Petkov
2026-10-12 14:03 ` Yazen Ghannam
2026-10-17 19:51 ` Borislav Petkov
2026-10-18 22:34 ` Yazen Ghannam
2026-10-18 23:07 ` Borislav Petkov [this message]
2026-10-19 2:16 ` Guixiong Wei
2026-10-19 4:19 ` Borislav Petkov
2026-10-19 13:05 ` 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=20261018230751.GBatVRR1NLJCBJrLIB@fat_crate.local \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=weiguixiong@bytedance.com \
--cc=yazen.ghannam@amd.com \
/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®