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>, Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/entry changes for v5.4
Date: Mon, 16 Sep 2019 14:58:11 +0200 [thread overview]
Message-ID: <20190916125811.GA73360@gmail.com> (raw)
Linus,
Please pull the latest x86-entry-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-entry-for-linus
# HEAD: 6365b842aae4490ebfafadfc6bb27a6d3cc54757 x86/syscalls: Split the x32 syscalls into their own table
This tree contains x32 and compat syscall improvements, the biggest one
of which splits x32 syscalls into their own table, which allows new
syscalls to share the x32 and x86-64 number - which turns the 512-547
special syscall numbers range into a legacy wart that won't be extended
going forward.
Thanks,
Ingo
------------------>
Andy Lutomirski (4):
x86/syscalls: Make __X32_SYSCALL_BIT be unsigned long
x86/syscalls: Use the compat versions of rt_sigsuspend() and rt_sigprocmask()
x86/syscalls: Disallow compat entries for all types of 64-bit syscalls
x86/syscalls: Split the x32 syscalls into their own table
arch/x86/entry/common.c | 13 ++--
arch/x86/entry/syscall_64.c | 25 +++++++
arch/x86/entry/syscalls/syscall_32.tbl | 4 +-
arch/x86/entry/syscalls/syscalltbl.sh | 35 +++++-----
arch/x86/include/asm/syscall.h | 4 ++
arch/x86/include/asm/unistd.h | 6 --
arch/x86/include/uapi/asm/unistd.h | 2 +-
arch/x86/kernel/asm-offsets_64.c | 20 ++++++
tools/testing/selftests/x86/Makefile | 2 +-
tools/testing/selftests/x86/syscall_numbering.c | 89 +++++++++++++++++++++++++
10 files changed, 168 insertions(+), 32 deletions(-)
create mode 100644 tools/testing/selftests/x86/syscall_numbering.c
next reply other threads:[~2019-09-16 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 12:58 Ingo Molnar [this message]
2019-09-17 2:55 ` [GIT PULL] x86/entry changes for v5.4 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=20190916125811.GA73360@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox