From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/urgent for v5.19-rc8
Date: Sun, 24 Jul 2022 11:05:49 +0200 [thread overview]
Message-ID: <Yt0LbbTNZyrM0pVw@zn.tnic> (raw)
Hi Linus,
please pull a couple more retbleed fallout fixes.
It looks like their urgency is decreasing so it seems like we've managed
to catch whatever snafus the limited -rc testing has exposed. Maybe
we're getting ready... :)
Thx.
---
The following changes since commit ff6992735ade75aae3e35d16b17da1008d753d28:
Linux 5.19-rc7 (2022-07-17 13:30:22 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.19_rc8
for you to fetch changes up to b648ab487f31bc4c38941bc770ea97fe394304bb:
x86/speculation: Make all RETbleed mitigations 64-bit only (2022-07-23 18:45:11 +0200)
----------------------------------------------------------------
- Make retbleed mitigations 64-bit only (32-bit will need a bit more
work if even needed, at all).
- Prevent return thunks patching of the LKDTM modules as it is not needed there
- Avoid writing the SPEC_CTRL MSR on every kernel entry on eIBRS parts
- Enhance error output of apply_returns() when it fails to patch a return thunk
- A sparse fix to the sev-guest module
- Protect EFI fw calls by issuing an IBPB on AMD
----------------------------------------------------------------
Ben Hutchings (1):
x86/speculation: Make all RETbleed mitigations 64-bit only
Josh Poimboeuf (1):
lkdtm: Disable return thunks in rodata.c
Kees Cook (1):
x86/alternative: Report missing return thunk details
Pawan Gupta (1):
x86/bugs: Warn when "ibrs" mitigation is selected on Enhanced IBRS parts
Peter Zijlstra (1):
x86/amd: Use IBPB for firmware calls
Tom Lendacky (1):
virt: sev-guest: Pass the appropriate argument type to iounmap()
arch/x86/Kconfig | 8 ++++----
arch/x86/Makefile | 1 +
arch/x86/include/asm/cpufeatures.h | 1 +
arch/x86/include/asm/nospec-branch.h | 2 ++
arch/x86/kernel/alternative.c | 4 +++-
arch/x86/kernel/cpu/bugs.c | 14 +++++++++++++-
drivers/misc/lkdtm/Makefile | 9 ++++++---
drivers/virt/coco/sev-guest/sev-guest.c | 9 ++++++---
8 files changed, 36 insertions(+), 12 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-07-24 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 9:05 Borislav Petkov [this message]
2022-07-24 17:01 ` [GIT PULL] x86/urgent for v5.19-rc8 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=Yt0LbbTNZyrM0pVw@zn.tnic \
--to=bp@suse.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