From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: rene@exactcode.de, stable@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs" failed to apply to 4.14-stable tree
Date: Mon, 16 Oct 2023 10:12:26 +0200 [thread overview]
Message-ID: <2023101619-magnetic-king-3962@gregkh> (raw)
In-Reply-To: <20231016075537.GBZSzseVhKAg9674XP@fat_crate.local>
On Mon, Oct 16, 2023 at 09:55:37AM +0200, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> Date: Sat, 7 Oct 2023 12:57:02 +0200
> Subject: [PATCH] x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> Upstream commit f454b18e07f518bcd0c05af17a2239138bff52de.
>
> Fix erratum #1485 on Zen4 parts where running with STIBP disabled can
> cause an #UD exception. The performance impact of the fix is negligible.
>
> Reported-by: René Rebe <rene@exactcode.de>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Tested-by: René Rebe <rene@exactcode.de>
> Cc: <stable@kernel.org>
> Link: https://lore.kernel.org/r/D99589F4-BC5D-430B-87B2-72C20370CF57@exactcode.com
> ---
> arch/x86/include/asm/msr-index.h | 4 ++++
> arch/x86/kernel/cpu/amd.c | 9 +++++++++
> 2 files changed, 13 insertions(+)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-10-16 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 18:17 FAILED: patch "[PATCH] x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs" failed to apply to 4.14-stable tree gregkh
2023-10-16 7:55 ` Borislav Petkov
2023-10-16 8:12 ` Greg KH [this message]
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=2023101619-magnetic-king-3962@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=rene@exactcode.de \
--cc=stable@kernel.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.