From: James Morse <james.morse@arm.com>
To: Douglas Anderson <dianders@chromium.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Roxana Bradescu <roxabee@google.com>,
Julius Werner <jwerner@chromium.org>,
bjorn.andersson@oss.qualcomm.com,
Trilok Soni <quic_tsoni@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Scott Bauer <sbauer@quicinc.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/5] arm64: errata: Add newer ARM cores to the spectre_bhb_loop_affected() lists
Date: Wed, 29 Jan 2025 16:43:34 +0000 [thread overview]
Message-ID: <af19e188-97d1-42a1-aa2f-4792784c701b@arm.com> (raw)
In-Reply-To: <20250107120555.v4.5.I4a9a527e03f663040721c5401c41de587d015c82@changeid>
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@vger.kernel.org
Reviewed-by: James Morse <james.morse@arm.com>
Thanks!
James
next prev parent reply other threads:[~2025-01-29 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 20:05 [PATCH v4 0/5] arm64: errata: Rework Spectre BHB mitigations to not assume "safe" Douglas Anderson
2025-01-07 20:05 ` [PATCH v4 1/5] arm64: errata: Add QCOM_KRYO_4XX_GOLD to the spectre_bhb_k24_list Douglas Anderson
2025-02-07 22:56 ` Trilok Soni
2025-01-07 20:05 ` [PATCH v4 2/5] arm64: errata: Assume that unknown CPUs _are_ vulnerable to Spectre BHB Douglas Anderson
2025-01-29 16:43 ` James Morse
2025-01-29 19:14 ` Doug Anderson
2025-02-12 17:52 ` Catalin Marinas
2025-02-12 18:05 ` Doug Anderson
2025-01-07 20:06 ` [PATCH v4 3/5] arm64: errata: Add KRYO 2XX/3XX/4XX silver cores to Spectre BHB safe list Douglas Anderson
2025-02-07 22:57 ` Trilok Soni
2025-01-07 20:06 ` [PATCH v4 4/5] arm64: cputype: Add MIDR_CORTEX_A76AE Douglas Anderson
2025-01-07 20:06 ` [PATCH v4 5/5] arm64: errata: Add newer ARM cores to the spectre_bhb_loop_affected() lists Douglas Anderson
2025-01-29 16:43 ` James Morse [this message]
2025-03-14 18:42 ` [PATCH v4 0/5] arm64: errata: Rework Spectre BHB mitigations to not assume "safe" Catalin Marinas
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=af19e188-97d1-42a1-aa2f-4792784c701b@arm.com \
--to=james.morse@arm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=florian.fainelli@broadcom.com \
--cc=jwerner@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=roxabee@google.com \
--cc=sbauer@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=will@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