From: Brian Gerst <brgerst@gmail.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>, Christoph Hellwig <hch@lst.de>,
Arnd Bergmann <arnd@arndb.de>, Brian Gerst <brgerst@gmail.com>
Subject: [PATCH 0/2] X32 syscall cleanups
Date: Tue, 16 Jun 2020 10:23:13 -0400 [thread overview]
Message-ID: <20200616142315.375918-1-brgerst@gmail.com> (raw)
Christoph Hellwig uncovered an issue with how we currently handle X32
syscalls. Currently, we can only use COMPAT_SYS_DEFINEx() for X32
specific syscalls. These changes remove that restriction and allow
native syscalls.
Brian Gerst (2):
x86/x32: Use __x64 prefix for X32 compat syscalls
x86/x32: Convert x32_rt_sigreturn to native syscall
arch/x86/entry/syscall_x32.c | 8 +++-----
arch/x86/entry/syscalls/syscall_64.tbl | 2 +-
arch/x86/include/asm/syscall_wrapper.h | 10 +++++-----
arch/x86/kernel/signal.c | 2 +-
tools/perf/arch/x86/entry/syscalls/syscall_64.tbl | 2 +-
5 files changed, 11 insertions(+), 13 deletions(-)
base-commit: 83cdaef93988a6bc6875623781de571b2694fe02
--
2.26.2
next reply other threads:[~2020-06-16 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 14:23 Brian Gerst [this message]
2020-06-16 14:23 ` [PATCH 1/2] x86/x32: Use __x64 prefix for X32 compat syscalls Brian Gerst
2020-06-16 16:49 ` Andy Lutomirski
2020-06-16 17:17 ` Brian Gerst
2020-06-23 20:49 ` hpa
2020-06-16 14:23 ` [PATCH 2/2] x86/x32: Convert x32_rt_sigreturn to native syscall Brian Gerst
2020-07-14 6:40 ` [PATCH 0/2] X32 syscall cleanups Christoph Hellwig
2020-07-14 17:02 ` Brian Gerst
2020-07-14 17:41 ` Andy Lutomirski
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=20200616142315.375918-1-brgerst@gmail.com \
--to=brgerst@gmail.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).