From: Borislav Petkov <bp@alien8.de>
To: Aristeu Rozanski <aris@redhat.com>
Cc: linux-edac@vger.kernel.org, mchehab@kernel.org
Subject: Re: [RESEND PATCH] i5000_edac: fix slot number passed to determine_mtr()
Date: Thu, 22 Sep 2022 15:55:57 +0200 [thread overview]
Message-ID: <YyxpbRkuLPIcW1Om@zn.tnic> (raw)
In-Reply-To: <20220922134659.biiy6g743qplzgiq@redhat.com>
On Thu, Sep 22, 2022 at 09:46:59AM -0400, Aristeu Rozanski wrote:
> I'm only fixing a out of bounds access, on purpose.
> Look at 64e1fdaf55d6 and the new version of determine_mtr().
I have been looking at that one. And I'm questioning it:
"The logic there is broken: it basically creates two csrows for each
DIMM and assumes that all DIMM's are dual rank."
That commit message doesn't explain why this assumption is wrong.
Furthermore, "If single rank memories are found, they'll be marked with
0 bytes."
So this looks to me like this commit is breaking dual-ranked DIMMs
configs in order to fix single-ranked ones.
> And this is the reason why I decided to not do it. We do have the hardware
> but last time I checked none of them had functional EINJ.
You don't need EINJ - there's arch/x86/kernel/cpu/mce/inject.c with
which you can do sw-only injection to test the decoding paths.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-09-22 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 18:10 [RESEND PATCH] i5000_edac: fix slot number passed to determine_mtr() Aristeu Rozanski
2022-09-21 19:38 ` Borislav Petkov
2022-09-22 13:46 ` Aristeu Rozanski
2022-09-22 13:55 ` Borislav Petkov [this message]
2022-09-26 16:51 ` Aristeu Rozanski
2022-09-26 18:02 ` Borislav Petkov
2022-09-28 12:48 ` [PATCH] i5000_edac: mark as BROKEN Aristeu Rozanski
2022-10-17 14:41 ` Borislav Petkov
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=YyxpbRkuLPIcW1Om@zn.tnic \
--to=bp@alien8.de \
--cc=aris@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@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