From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/bugs for v7.4-rc1
Date: Mon, 19 Oct 2026 18:12:22 -0700 [thread overview]
Message-ID: <20261020011222.GAata_9v7y26cjCQfW@fat_crate.local> (raw)
Hi Linus,
please pull the x86 spec bugs lineup for v7.4-rc1.
Thx.
---
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_bugs_for_v7.4_rc1
for you to fetch changes up to 1847c80537891baead3975f3ca969233ff7b2a11:
x86/bugs: Fix CONFIG_MITIGATION_RETPOLINE=n mitigation reporting (2026-10-02 15:48:29 -0700)
----------------------------------------------------------------
- AMD Zen6's BTB has per-context tagging so there's no need for the expensive
SRSO SafeRET mitigation anymore; add glue to detect and handle that
- Fix Spectre v2 mitigation reporting for RETPOLINE=n builds
----------------------------------------------------------------
Borislav Petkov (AMD) (1):
x86/bugs: Adapt SRSO mitigation to Zen6
Kim Phillips (1):
x86/bugs: Fix CONFIG_MITIGATION_RETPOLINE=n mitigation reporting
arch/x86/include/asm/cpufeatures.h | 1 +
arch/x86/kernel/cpu/bugs.c | 20 +++++++++++++++++---
arch/x86/kernel/cpu/scattered.c | 1 +
3 files changed, 19 insertions(+), 3 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2026-10-20 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 1:12 Borislav Petkov [this message]
2026-10-20 21:38 ` pr-tracker-bot
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=20261020011222.GAata_9v7y26cjCQfW@fat_crate.local \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®