From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/asm changes for v5.3
Date: Mon, 8 Jul 2019 14:22:47 +0200 [thread overview]
Message-ID: <20190708122247.GA57237@gmail.com> (raw)
Linus,
Please pull the latest x86-asm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-for-linus
# HEAD: 7457c0da024b181a9143988d740001f9bc98698d x86/alternatives: Add int3_emulate_call() selftest
Most of the changes relate to Peter Zijlstra's cleanup of ptregs
handling, in particular the i386 part is now much simplified and
standardized - no more partial ptregs stack frames via the esp/ss oddity.
This simplifies ftrace, kprobes, the unwinder, ptrace, kdump and kgdb.
There's also a CR4 hardening enhancements by Kees Cook, to make the
generic platform functions such as native_write_cr4() less useful as ROP
gadgets that disable SMEP/SMAP. Also protect the WP bit of CR0 against
similar attacks.
The rest is smaller cleanups/fixes.
Thanks,
Ingo
------------------>
Ira Weiny (1):
Documentation/x86: Fix path to entry_32.S
Kees Cook (2):
x86/asm: Pin sensitive CR4 bits
x86/asm: Pin sensitive CR0 bits
Peter Zijlstra (7):
x86/entry/32: Clean up return from interrupt preemption path
x86/stackframe: Move ENCODE_FRAME_POINTER to asm/frame.h
x86/stackframe, x86/kprobes: Fix frame pointer annotations
x86/stackframe, x86/ftrace: Add pt_regs frame annotations
x86/stackframe/32: Provide consistent pt_regs
x86/stackframe/32: Allow int3_emulate_push()
x86/alternatives: Add int3_emulate_call() selftest
Steven Rostedt (VMware) (1):
x86/asm: Remove unused TASK_TI_flags from asm-offsets.c
Documentation/x86/exception-tables.rst | 2 +-
arch/x86/entry/calling.h | 15 ----
arch/x86/entry/entry_32.S | 145 ++++++++++++++++++++++++---------
arch/x86/include/asm/frame.h | 49 +++++++++++
arch/x86/include/asm/kexec.h | 17 ----
arch/x86/include/asm/ptrace.h | 17 +---
arch/x86/include/asm/special_insns.h | 37 ++++++++-
arch/x86/include/asm/stacktrace.h | 2 +-
arch/x86/include/asm/text-patching.h | 2 -
arch/x86/kernel/alternative.c | 81 +++++++++++++++++-
arch/x86/kernel/asm-offsets.c | 1 -
arch/x86/kernel/cpu/common.c | 20 +++++
arch/x86/kernel/crash.c | 8 --
arch/x86/kernel/ftrace.c | 7 --
arch/x86/kernel/ftrace_32.S | 78 ++++++++++--------
arch/x86/kernel/ftrace_64.S | 3 +
arch/x86/kernel/kgdb.c | 8 --
arch/x86/kernel/kprobes/common.h | 28 +++----
arch/x86/kernel/kprobes/core.c | 29 +++----
arch/x86/kernel/kprobes/opt.c | 20 +++--
arch/x86/kernel/process_32.c | 16 ++--
arch/x86/kernel/ptrace.c | 29 -------
arch/x86/kernel/smpboot.c | 8 +-
arch/x86/kernel/time.c | 3 +-
arch/x86/kernel/unwind_frame.c | 32 +-------
arch/x86/kernel/unwind_orc.c | 2 +-
26 files changed, 394 insertions(+), 265 deletions(-)
next reply other threads:[~2019-07-08 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 12:22 Ingo Molnar [this message]
2019-07-09 1:45 ` [GIT PULL] x86/asm changes for v5.3 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=20190708122247.GA57237@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.