linux-kernel - Re: [PATCH] EDAC/amd64: Fix possible module load failure on some UMC usage combinations

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <a3990569-ebf8-4c6e-95f7-851312ea823f@amd.com>
Date: Tue, 10 Dec 2024 11:32:06 -0600
From: "Naik, Avadhut" <avadnaik@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
 yazen.ghannam@....com, Avadhut Naik <avadhut.naik@....com>
Subject: Re: [PATCH] EDAC/amd64: Fix possible module load failure on some UMC
 usage combinations



On 12/10/2024 03:55, Borislav Petkov wrote:
> On Mon, Dec 09, 2024 at 09:55:10PM +0000, Avadhut Naik wrote:
>> Starting Zen4, AMD SOCs have 12 Unified Memory Controllers (UMCs) per
>> socket.
>>
>> When the amd64_edac module is being loaded, these UMCs are traversed to
>> determine if they have SdpInit (SdpCtrl[31]) and EccEnabled (UmcCapHi[30])
>> bits set and create masks in umc_en_mask and ecc_en_mask respectively.
>>
>> However, the current data type of these variables is u8. As a result, if
>> only the last 4 UMCs (UMC8 - UMC11) of the system have been utilized,
>> umc_ecc_enabled() will return false. Consequently, the module may fail to
>> load on these systems.
>>
>> Change the data type of these variables to u16.
> 
> No need to explain what the patch does. The "why" is enough.
>  
Will remove this line.

>> Signed-off-by: Avadhut Naik <avadhut.naik@....com>
>> ---
>>  drivers/edac/amd64_edac.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> This looks like it needs a CC:stable and a Fixes: tag, right?
> 
It does need a Fixes: tag. Will add that.
But not so sure about the CC:stable.
Quoting from stable-kernel-rules about the patches that are accepted into stable.

It must fix a real bug that bothers people (not a, “This could be a problem...” type thing).

This has not been reported by anyone yet. IMO, it classifies as
"This could be a problem" type issue.
Would you agree?

> While at it, you can simply make those vars int and be done with it.
> 
Okay, will change the data type of these 2 variables to int.
> Thx.
> 

-- 
Thanks,
Avadhut Naik