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.13-rc6
Date: Sun, 20 Jun 2021 08:59:31 +0200 [thread overview]
Message-ID: <YM7nUwsJ+1v66B9m@zn.tnic> (raw)
Hi Linus,
here are some x86/urgent fixes before 5.13 releases. This time, I'm not
even going to think of saying that they're the last batch. :)
Please pull,
thx.
---
The following changes since commit 614124bea77e452aa6df7a8714e8bc820b489922:
Linux 5.13-rc5 (2021-06-06 15:47:27 -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.13_rc6
for you to fetch changes up to 28e5e44aa3f4e0e0370864ed008fb5e2d85f4dc8:
x86/mm: Avoid truncating memblocks for SGX memory (2021-06-18 19:37:01 +0200)
----------------------------------------------------------------
A first set of urgent fixes to the FPU/XSTATE handling mess^W code.
(There's a lot more in the pipe):
- Prevent corruption of the XSTATE buffer in signal handling by
validating what is being copied from userspace first.
- Invalidate other task's preserved FPU registers on XRSTOR failure
(#PF) because latter can still modify some of them.
- Restore the proper PKRU value in case userspace modified it
- Reset FPU state when signal restoring fails
Other:
- Map EFI boot services data memory as encrypted in a SEV guest so that
the guest can access it and actually boot properly
- Two SGX correctness fixes: proper resources freeing and a NUMA fix
----------------------------------------------------------------
Andy Lutomirski (1):
x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer
Fan Du (1):
x86/mm: Avoid truncating memblocks for SGX memory
Kai Huang (1):
x86/sgx: Add missing xa_destroy() when virtual EPC is destroyed
Thomas Gleixner (4):
x86/fpu: Prevent state corruption in __fpu__restore_sig()
x86/process: Check PF_KTHREAD and not current->mm for kernel threads
x86/pkru: Write hardware init value to PKRU when xstate is init
x86/fpu: Reset state for all signal restore failures
Tom Lendacky (1):
x86/ioremap: Map EFI-reserved memory as encrypted for SEV
arch/x86/include/asm/fpu/internal.h | 13 ++++++---
arch/x86/kernel/cpu/sgx/virt.c | 1 +
arch/x86/kernel/fpu/signal.c | 54 ++++++++++++++++++++++++-------------
arch/x86/mm/ioremap.c | 4 ++-
arch/x86/mm/numa.c | 8 +++++-
5 files changed, 56 insertions(+), 24 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2021-06-20 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 6:59 Borislav Petkov [this message]
2021-06-20 16:49 ` 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=YM7nUwsJ+1v66B9m@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
all inboxes | Powered by JetHome®