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 5.8-rc3
Date: Sun, 28 Jun 2020 16:43:19 +0200 [thread overview]
Message-ID: <20200628144319.GD18884@zn.tnic> (raw)
Hi Linus,
please pull the x86/urgent pile which has nothing but clear fixes.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_5.8_rc3
for you to fetch changes up to bb5570ad3b54e7930997aec76ab68256d5236d94:
x86/asm/64: Align start of __clear_user() loop to 16-bytes (2020-06-19 18:32:11 +0200)
----------------------------------------------------------------
* AMD Memory bandwidth counter width fix, by Babu Moger.
* Use the proper length type in the 32-bit truncate() syscall variant,
by Jiri Slaby.
* Reinit IA32_FEAT_CTL during wakeup to fix the case where after
resume, VMXON would #GP due to VMX not being properly enabled, by Sean
Christopherson.
* Fix a static checker warning in the resctrl code, by Dan Carpenter.
* Add a CR4 pinning mask for bits which cannot change after boot, by
Kees Cook.
* Align the start of the loop of __clear_user() to 16 bytes, to improve
performance on AMD zen1 and zen2 microarchitectures, by Matt Fleming.
----------------------------------------------------------------
Babu Moger (1):
x86/resctrl: Fix memory bandwidth counter width for AMD
Dan Carpenter (1):
x86/resctrl: Fix a NULL vs IS_ERR() static checker warning in rdt_cdp_peer_get()
Jiri Slaby (1):
syscalls: Fix offset type of ksys_ftruncate()
Kees Cook (1):
x86/cpu: Use pinning mask for CR4 bits needing to be 0
Matt Fleming (1):
x86/asm/64: Align start of __clear_user() loop to 16-bytes
Sean Christopherson (1):
x86/cpu: Reinitialize IA32_FEAT_CTL MSR on BSP during wakeup
arch/x86/include/asm/cpu.h | 5 +++++
arch/x86/kernel/cpu/centaur.c | 1 +
arch/x86/kernel/cpu/common.c | 24 ++++++++++++------------
arch/x86/kernel/cpu/cpu.h | 4 ----
arch/x86/kernel/cpu/resctrl/core.c | 8 ++++----
arch/x86/kernel/cpu/resctrl/internal.h | 1 +
arch/x86/kernel/cpu/resctrl/rdtgroup.c | 1 +
arch/x86/kernel/cpu/zhaoxin.c | 1 +
arch/x86/lib/usercopy_64.c | 1 +
arch/x86/power/cpu.c | 6 ++++++
include/linux/syscalls.h | 2 +-
11 files changed, 33 insertions(+), 21 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-06-28 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 14:43 Borislav Petkov [this message]
2020-06-28 18:45 ` [GIT PULL] x86/urgent for 5.8-rc3 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=20200628144319.GD18884@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