From: Catalin Marinas <catalin.marinas@arm.com>
To: Doug Anderson <dianders@chromium.org>
Cc: James Morse <james.morse@arm.com>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
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 2/5] arm64: errata: Assume that unknown CPUs _are_ vulnerable to Spectre BHB
Date: Wed, 12 Feb 2025 17:52:29 +0000 [thread overview]
Message-ID: <Z6zf3YJq6qqoJQRi@arm.com> (raw)
In-Reply-To: <CAD=FV=WTe-yULo9iVUX-4o8cskPNp8dK-N9pKq6MxqrPX3UMGw@mail.gmail.com>
On Wed, Jan 29, 2025 at 11:14:20AM -0800, Doug Anderson wrote:
> On Wed, Jan 29, 2025 at 8:43 AM James Morse <james.morse@arm.com> wrote:
> > Arm have recently updated that table of CPUs
> > with extra entries (thanks for picking those up!) - but now that patch can't be easily
> > applied to older kernels.
> > I suspect making the reporting assuming-vulnerable may make other CPUs come out of the
> > wood work too...
> >
> > Could we avoid changing this unless we really need to?
>
> Will / Catalin: Do either of you have an opinion here?
Is this about whether to report "vulnerable" for unknown CPUs? I think
Will suggested this:
https://lore.kernel.org/all/20241219175128.GA25477@willie-the-truck/
That said, some patch splitting will help to make review easier. Should
such change be back-portable as well? I think so, it's not only for CPUs
we'll see in the future.
--
Catalin
next prev parent reply other threads:[~2025-02-12 17:55 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 [this message]
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
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=Z6zf3YJq6qqoJQRi@arm.com \
--to=catalin.marinas@arm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=dianders@chromium.org \
--cc=florian.fainelli@broadcom.com \
--cc=james.morse@arm.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