Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: [PATCH] Update 212c2020833b ("iommu/amd: Force device table to maximum size")
Date: Mon, 16 Nov 2026 09:09:29 +0100	[thread overview]
Message-ID: <20261116080929.108901-1-joro@8bytes.org> (raw)
In-Reply-To: <2026-11-11-1-daily-reply-0020-75e008cc30c56605257c@kernel.org>

From: Joerg Roedel <joerg.roedel@amd.com>

commit 6e2213dae78b41976c60133eb10cf99e81916638 upstream.

The stable backport for the commit in the subject line lacks a hunk to
match the fix on all relevant hardware generations. Add the missing
hunk.

Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
---
 arch/x86/kernel/cpu/amd.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
index bd274c2b4c6a..ef55c76a3906 100644
--- a/arch/x86/kernel/cpu/amd.c
+++ b/arch/x86/kernel/cpu/amd.c
@@ -524,6 +524,7 @@ static void bsp_init_amd(struct cpuinfo_x86 *c)
 		case 0x50 ... 0x5f:
 		case 0x80 ... 0xaf:
 		case 0xc0 ... 0xcf:
+		case 0xd8 ... 0xef:
 			setup_force_cpu_cap(X86_FEATURE_ZEN6);
 			break;
 		default:
-- 
2.53.0


      reply	other threads:[~2026-11-16  8:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 10:39 Linux-stable backports for IOMMU CVE-2024-21963 Jörg Rödel
2026-11-11 10:39 ` [PATCH 6.18.y] iommu/amd: Force device table to maximum size Jörg Rödel
2026-11-11 10:39 ` [PATCH 6.12.y] " Jörg Rödel
2026-11-11 10:39 ` [PATCH 6.6.y] " Jörg Rödel
2026-11-11 10:39 ` [PATCH 6.1.y] " Jörg Rödel
2026-11-11 10:40 ` [PATCH 5.15.y] " Jörg Rödel
2026-11-11 10:40 ` [PATCH 5.10.y] " Jörg Rödel
2026-11-11 21:54 ` Linux-stable backports for IOMMU CVE-2024-21963 Sasha Levin
2026-11-16  8:09   ` Jörg Rödel [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=20261116080929.108901-1-joro@8bytes.org \
    --to=joro@8bytes.org \
    --cc=joerg.roedel@amd.com \
    --cc=sashal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox