From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: [GIT PULL] x86/entry changes for v6.8
Date: Mon, 8 Jan 2024 12:30:15 +0100 [thread overview]
Message-ID: <ZZvcx3N1KxL2GBb8@gmail.com> (raw)
Linus,
Please pull the latest x86/entry git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-entry-2024-01-08
# HEAD: 1e4d3001f59fb7a9917cb746544b65e616b5f809 x86/entry: Harden return-to-user
x86/entry changes for v6.8:
- Optimize common_interrupt_return()
- Harden the return-to-user code by making a CONFIG_DEBUG_ENTRY=y
check unconditional & moving it closer to the IRET.
Thanks,
Ingo
------------------>
Peter Zijlstra (2):
x86/entry: Optimize common_interrupt_return()
x86/entry: Harden return-to-user
arch/x86/entry/calling.h | 12 +++++++++---
arch/x86/entry/entry_64.S | 33 ++++++++++++++++++++++-----------
2 files changed, 31 insertions(+), 14 deletions(-)
next reply other threads:[~2024-01-08 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 11:30 Ingo Molnar [this message]
2024-01-09 2:11 ` [GIT PULL] x86/entry changes for v6.8 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=ZZvcx3N1KxL2GBb8@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 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.