All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Morse <james.morse@arm.com>
Cc: stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [stable:PATCH v5.4.225 0/2] arm64: errata: Spectre-BHB fixes
Date: Sat, 3 Dec 2022 14:32:39 +0100	[thread overview]
Message-ID: <Y4tP9+uUkOPhvSUZ@kroah.com> (raw)
In-Reply-To: <20221130182819.739068-1-james.morse@arm.com>

On Wed, Nov 30, 2022 at 06:28:17PM +0000, James Morse wrote:
> Hello!
> 
> The first patch fixes an issue reported by Sami, where linux panic()s
> when bringing secondary CPUs online. The problem was the Spectre
> workarounds trying to allocate a new slot for mitigating KVM when
> those pages are no longer writeable.
> 
> While debugging that issue, I spotted the Spectre-BHB KVM mitigation was
> over-riding the Spectre-v2 KVM Mitigation. It's supposed to happen the
> other way round.
> 
> The backports aren't the same as mainline because the spectre mitigation code
> was totally rewritten for v5.10, and prior to that the KVM infrastructure
> is very different.

All now queued up, thanks.

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: James Morse <james.morse@arm.com>
Cc: stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [stable:PATCH v5.4.225 0/2] arm64: errata: Spectre-BHB fixes
Date: Sat, 3 Dec 2022 14:32:39 +0100	[thread overview]
Message-ID: <Y4tP9+uUkOPhvSUZ@kroah.com> (raw)
In-Reply-To: <20221130182819.739068-1-james.morse@arm.com>

On Wed, Nov 30, 2022 at 06:28:17PM +0000, James Morse wrote:
> Hello!
> 
> The first patch fixes an issue reported by Sami, where linux panic()s
> when bringing secondary CPUs online. The problem was the Spectre
> workarounds trying to allocate a new slot for mitigating KVM when
> those pages are no longer writeable.
> 
> While debugging that issue, I spotted the Spectre-BHB KVM mitigation was
> over-riding the Spectre-v2 KVM Mitigation. It's supposed to happen the
> other way round.
> 
> The backports aren't the same as mainline because the spectre mitigation code
> was totally rewritten for v5.10, and prior to that the KVM infrastructure
> is very different.

All now queued up, thanks.

greg k-h

_______________________________________________
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-12-03 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 18:28 [stable:PATCH v5.4.225 0/2] arm64: errata: Spectre-BHB fixes James Morse
2022-11-30 18:28 ` James Morse
2022-11-30 18:28 ` [stable:PATCH v5.4.225 1/2] arm64: Fix panic() when Spectre-v2 causes Spectre-BHB to re-allocate KVM vectors James Morse
2022-11-30 18:28   ` James Morse
2022-12-03 13:55   ` Patch "arm64: Fix panic() when Spectre-v2 causes Spectre-BHB to re-allocate KVM vectors" has been added to the 5.4-stable tree gregkh
2022-11-30 18:28 ` [stable:PATCH v5.4.225 2/2] arm64: errata: Fix KVM Spectre-v2 mitigation selection for Cortex-A57/A72 James Morse
2022-11-30 18:28   ` James Morse
2022-12-03 13:55   ` Patch "arm64: errata: Fix KVM Spectre-v2 mitigation selection for Cortex-A57/A72" has been added to the 5.4-stable tree gregkh
2022-12-03 13:32 ` Greg KH [this message]
2022-12-03 13:32   ` [stable:PATCH v5.4.225 0/2] arm64: errata: Spectre-BHB fixes Greg KH

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=Y4tP9+uUkOPhvSUZ@kroah.com \
    --to=greg@kroah.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=stable@vger.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.