All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, ardb@kernel.org,
	broonie@kernel.org, catalin.marinas@arm.com, james.morse@arm.com,
	will@kernel.org
Subject: Re: [PATCH] arm64: prevent instrumentation of bp hardening callbacks
Date: Fri, 25 Feb 2022 13:52:35 +0000	[thread overview]
Message-ID: <87o82v2gv0.wl-maz@kernel.org> (raw)
In-Reply-To: <20220224181028.512873-1-mark.rutland@arm.com>

On Thu, 24 Feb 2022 18:10:28 +0000,
Mark Rutland <mark.rutland@arm.com> wrote:
> 
> We may call arm64_apply_bp_hardening() early during entry (e.g. in
> el0_ia()) before it is safe to run instrumented code. Unfortunately this
> may result in running instrumented code in two cases:

[...]

> Fixes: ec82b567a74fbdff ("arm64: Implement branch predictor hardening for Falkor")
> Fixes: b092201e00206141 ("arm64: Add ARM_SMCCC_ARCH_WORKAROUND_1 BP hardening support")
> Fixes: d4647f0a2ad71110 ("arm64: Rewrite Spectre-v2 mitigation code")
> Fixes: 0f15adbb2861ce6f ("arm64: Add skeleton to harden the branch predictor against aliasing attacks")
> Fixes: 6279017e807708a0 ("KVM: arm64: Move BP hardening helpers into spectre.h")
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: James Morse <james.morse@arm.com>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Will Deacon <will@kernel.org>

Acked-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-02-25 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 18:10 [PATCH] arm64: prevent instrumentation of bp hardening callbacks Mark Rutland
2022-02-25 13:14 ` Mark Brown
2022-02-25 13:52 ` Marc Zyngier [this message]
2022-03-07 22:03 ` Will Deacon

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=87o82v2gv0.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.