From: David Kaplan <david.kaplan@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/5] Bugs clean-up
Date: Tue, 19 Aug 2025 14:21:55 -0500 [thread overview]
Message-ID: <20250819192200.2003074-1-david.kaplan@amd.com> (raw)
Patches 1-3 focus on cleaning up parameter parsing. Most mitigations use
early_param but a few older ones do not and look at boot_command_line
directly. Modify those to be consistent with the newer ones.
Patch 4 adds missing attack vector controls for spec store bypass.
Patch 5 cleans up straggling unnecessary calls to cpu_mitigations_off().
Changes from v1
- Removed spec_*_print_cond() functions
- Fixed bugs pointed out by Pawan
- Added last 2 patches
David Kaplan (5):
x86/bugs: Use early_param for spectre_v2_user
x86/bugs: Use early_param for spectre_v2
x86/bugs: Simplify SSB cmdline parsing
x86/bugs: Add attack vector controls for SSB
x86/bugs: Remove uses of cpu_mitigations_off()
.../hw-vuln/attack_vector_controls.rst | 5 +-
arch/x86/include/asm/nospec-branch.h | 1 +
arch/x86/kernel/cpu/bugs.c | 387 ++++++++----------
3 files changed, 169 insertions(+), 224 deletions(-)
base-commit: 2fd6a6194558303fffd2d7a7fa73fc318d680f38
--
2.34.1
next reply other threads:[~2025-08-19 19:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 19:21 David Kaplan [this message]
2025-08-19 19:21 ` [PATCH v2 1/5] x86/bugs: Use early_param for spectre_v2_user David Kaplan
2025-08-20 18:37 ` Borislav Petkov
2025-08-27 21:51 ` Josh Poimboeuf
2025-08-27 21:59 ` Kaplan, David
2025-08-19 19:21 ` [PATCH v2 2/5] x86/bugs: Use early_param for spectre_v2 David Kaplan
2025-08-22 11:49 ` Borislav Petkov
2025-08-22 14:12 ` Kaplan, David
2025-08-22 14:30 ` Borislav Petkov
2025-08-22 14:37 ` Kaplan, David
2025-08-19 19:21 ` [PATCH v2 3/5] x86/bugs: Simplify SSB cmdline parsing David Kaplan
2025-08-27 22:02 ` Josh Poimboeuf
2025-08-19 19:21 ` [PATCH v2 4/5] x86/bugs: Add attack vector controls for SSB David Kaplan
2025-08-21 6:17 ` Pawan Gupta
2025-08-27 10:27 ` Borislav Petkov
2025-08-27 11:04 ` Borislav Petkov
2025-08-27 14:05 ` Kaplan, David
2025-08-27 14:22 ` Borislav Petkov
2025-08-27 14:25 ` Kaplan, David
2025-08-27 15:33 ` Borislav Petkov
2025-08-27 15:47 ` Kaplan, David
2025-08-27 16:11 ` Borislav Petkov
2025-08-27 16:15 ` Kaplan, David
2025-08-27 16:19 ` Borislav Petkov
2025-08-28 13:39 ` [tip: x86/urgent] " tip-bot2 for David Kaplan
2025-08-19 19:22 ` [PATCH v2 5/5] x86/bugs: Remove uses of cpu_mitigations_off() David Kaplan
2025-08-21 6:18 ` [PATCH v2 0/5] Bugs clean-up Pawan Gupta
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=20250819192200.2003074-1-david.kaplan@amd.com \
--to=david.kaplan@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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®