From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Jonathan Marek <jonathan@marek.ca>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Douglas Anderson <dianders@chromium.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
shechenglong <shechenglong@xfusion.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Shameer Kolothum <skolothumtho@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: proton-pack: Fix hard lockup when !MITIGATE_SPECTRE_BRANCH_HISTORY
Date: Mon, 24 Nov 2025 14:41:02 +0000 [thread overview]
Message-ID: <176399113353.3273155.581458888814324419.b4-ty@kernel.org> (raw)
In-Reply-To: <20251117051211.16108-1-jonathan@marek.ca>
On Mon, 17 Nov 2025 00:12:08 -0500, Jonathan Marek wrote:
> The "drop print" commit removed the whole branch and not just the print.
> For some ARM64 cpus, this leads to hard lockup when
> CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY is not enabled.
>
>
Applied (with your SoB) to arm64 (for-next/fixes), thanks!
[1/1] arm64: proton-pack: Fix hard lockup when !MITIGATE_SPECTRE_BRANCH_HISTORY
https://git.kernel.org/arm64/c/165eb13e485c
I'd be inclined to remove CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY
entirely (i.e. make it unconditional) given the number of CPUs
affected and the dynamic controls we already have for the mitigation.
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2025-11-24 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 5:12 Jonathan Marek
2025-11-23 17:50 ` Jonathan Marek
2025-11-24 14:41 ` Will Deacon [this message]
2025-11-27 1:08 ` Vladimir Zapolskiy
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=176399113353.3273155.581458888814324419.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=james.morse@arm.com \
--cc=jonathan@marek.ca \
--cc=kernel-team@android.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tsoni@quicinc.com \
--cc=shechenglong@xfusion.com \
--cc=skolothumtho@nvidia.com \
/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
all inboxes | Powered by JetHome®