linux-kernel - Re: [PATCH v4 5/5] arm64: errata: Add newer ARM cores to the spectre_bhb_loop

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: <af19e188-97d1-42a1-aa2f-4792784c701b@arm.com>
Date: Wed, 29 Jan 2025 16:43:34 +0000
From: James Morse <james.morse@....com>
To: Douglas Anderson <dianders@...omium.org>,
 Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
 Mark Rutland <mark.rutland@....com>
Cc: Roxana Bradescu <roxabee@...gle.com>, Julius Werner
 <jwerner@...omium.org>, bjorn.andersson@....qualcomm.com,
 Trilok Soni <quic_tsoni@...cinc.com>, linux-arm-msm@...r.kernel.org,
 Florian Fainelli <florian.fainelli@...adcom.com>,
 linux-arm-kernel@...ts.infradead.org, Jeffrey Hugo <quic_jhugo@...cinc.com>,
 Scott Bauer <sbauer@...cinc.com>, stable@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 5/5] arm64: errata: Add newer ARM cores to the
 spectre_bhb_loop_affected() lists

Hi Doug,

On 07/01/2025 20:06, Douglas Anderson wrote:
> When comparing to the ARM list [1], it appears that several ARM cores
> were missing from the lists in spectre_bhb_loop_affected(). Add them.

It's a moving target!


> NOTE: for some of these cores it may not matter since other ways of
> clearing the BHB may be used (like the CLRBHB instruction or ECBHB),
> but it still seems good to have all the info from ARM's whitepaper
> included.
> 
> [1] https://developer.arm.com/Arm%20Security%20Center/Spectre-BHB
> 
> 
> Fixes: 558c303c9734 ("arm64: Mitigate spectre style branch history side channels")
> Cc: stable@...r.kernel.org

Reviewed-by: James Morse <james.morse@....com>


Thanks!

James