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.16-rc4 Date: Sun, 5 Dec 2021 12:09:28 +0100 [thread overview] Message-ID: <Yayd6FkzkKcOZKlc@zn.tnic> (raw) Hi Linus, please pull a bunch of x86/urgent fixes which accumulated in the last two weeks. Thx. --- The following changes since commit c0f2077baa4113f38f008b8e912b9fb3ff8d43df: x86/boot: Mark prepare_command_line() __init (2021-11-24 12:20:24 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.16_rc4 for you to fetch changes up to 5c8f6a2e316efebb3ba93d8c1af258155dcf5632: x86/xen: Add xenpv_restore_regs_and_return_to_usermode() (2021-12-03 19:21:15 +0100) ---------------------------------------------------------------- - Fix a couple of SWAPGS fencing issues in the x86 entry code - Use the proper operand types in __{get,put}_user() to prevent truncation in SEV-ES string io - Make sure the kernel mappings are present in trampoline_pgd in order to prevent any potential accesses to unmapped memory after switching to it - Fix a trivial list corruption in objtool's pv_ops validation - Disable the clocksource watchdog for TSC on platforms which claim that the TSC is constant, doesn't stop in sleep states, CPU has TSC adjust and the number of sockets of the platform are max 2, to prevent erroneous markings of the TSC as unstable. - Make sure TSC adjust is always checked not only when going idle - Prevent a stack leak by initializing struct _fpx_sw_bytes properly in the FPU code - Fix INTEL_FAM6_RAPTORLAKE define naming to adhere to the convention ---------------------------------------------------------------- Feng Tang (2): x86/tsc: Add a timer to make sure TSC_adjust is always checked x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Joerg Roedel (1): x86/64/mm: Map all kernel memory into trampoline_pgd Lai Jiangshan (3): x86/entry: Add a fence for kernel entry SWAPGS in paranoid_entry() x86/entry: Use the correct fence macro after swapgs in kernel CR3 x86/xen: Add xenpv_restore_regs_and_return_to_usermode() Marco Elver (1): x86/fpu/signal: Initialize sw_bytes in save_xstate_epilog() Michael Sterritt (1): x86/sev: Fix SEV-ES INS/OUTS instructions for word, dword, and qword Peter Zijlstra (1): objtool: Fix pv_ops noinstr validation Tony Luck (1): x86/cpu: Drop spurious underscore from RAPTOR_LAKE #define arch/x86/entry/entry_64.S | 35 +++++++++++------------ arch/x86/include/asm/intel-family.h | 2 +- arch/x86/kernel/fpu/signal.c | 2 +- arch/x86/kernel/sev.c | 57 +++++++++++++++++++++++++------------ arch/x86/kernel/tsc.c | 28 +++++++++++++++--- arch/x86/kernel/tsc_sync.c | 41 ++++++++++++++++++++++++++ arch/x86/realmode/init.c | 12 +++++++- arch/x86/xen/xen-asm.S | 20 +++++++++++++ tools/objtool/elf.c | 1 + tools/objtool/objtool.c | 4 +++ 10 files changed, 159 insertions(+), 43 deletions(-) -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2021-12-05 11:09 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-05 11:09 Borislav Petkov [this message] 2021-12-05 17:02 ` 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=Yayd6FkzkKcOZKlc@zn.tnic \ --to=bp@suse.de \ --cc=linux-kernel@vger.kernel.org \ --cc=torvalds@linux-foundation.org \ --cc=x86@kernel.org \ --subject='Re: [GIT PULL] x86/urgent for v5.16-rc4' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).