linux-kernel - RE: [PATCH 1/2] EDAC/skx_common: Distinguish the memory error source

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <SJ1PR11MB6083EE82968F5F6D8C8D2B84FC4E2@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 24 Oct 2024 17:33:39 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>
CC: Borislav Petkov <bp@...en8.de>, James Morse <james.morse@....com>, "Mauro
 Carvalho Chehab" <mchehab@...nel.org>, Robert Richter <rric@...nel.org>,
	"Garcia Rodriguez, Diego" <diego.garcia.rodriguez@...el.com>,
	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] EDAC/skx_common: Distinguish the memory error source

> The current skx_common determines whether the memory error source is the
> near memory of the 2LM system and then retrieves the decoded error results
> from the ADXL components (near-memory vs. non-near-memory) accordingly.
>
> However, some memory controllers may have limitations in correctly
> reporting the memory error source, leading to the retrieval of incorrect
> decoded parts from the ADXL.
>
> To address these limitations, instead of simply determining whether the
> memory error is from the near memory of the 2LM system, it is necessary to
> distinguish the memory error source details as follows:
>
>   Memory error from the near memory of the 2LM system.
>   Memory error from the far memory of the 2LM system.
>   Memory error from the 1LM system.
>   Not a memory error.
>
> This will enable the i10nm_edac driver to take appropriate actions for
> those memory controllers that have limitations in reporting the memory
> error source.
>
> Fixes: ba987eaaabf9 ("EDAC/i10nm: Add Intel Granite Rapids server support")
> Tested-by: Diego Garcia Rodriguez <diego.garcia.rodriguez@...el.com>
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@...el.com>


Applied (this one and part 2) to edac-drivers branch of RAS tree.

Thanks

-Tony