diff options
| author |  Masahiro Yamada <masahiroy@kernel.org>
| 2021-05-17 16:38:09 +0900 |
|---|---|---|
| committer |  Thomas Gleixner <tglx@linutronix.de>
| 2021-05-20 15:03:58 +0200 |
| commit | 2e958a8a510d956ec8528f0bd20e309b5bb5156c (patch) | |
| tree | 57661eec425dbdb46c183f12a7f1ae21fa95ed09 /arch/x86/um/sys_call_table_64.c | |
| parent | x86/asm: Make <asm/asm.h> valid on cross-builds as well (diff) | |
| download | linux-2e958a8a510d956ec8528f0bd20e309b5bb5156c.tar.gz linux-2e958a8a510d956ec8528f0bd20e309b5bb5156c.tar.bz2 linux-2e958a8a510d956ec8528f0bd20e309b5bb5156c.zip | |
x86/entry/x32: Rename __x32_compat_sys_* to __x64_compat_sys_*
The SYSCALL macros are mapped to symbols as follows:
__SYSCALL_COMMON(nr, sym) --> __x64_<sym>
__SYSCALL_X32(nr, sym) --> __x32_<sym>
Originally, the syscalls in the x32 special range (512-547) were all
compat.
This assumption is now broken after the following commits:
55db9c0e8534 ("net: remove compat_sys_{get,set}sockopt")
5f764d624a89 ("fs: remove the compat readv/writev syscalls")
598b3cec831f ("fs: remove compat_sys_vmsplice")
c3973b401ef2 ("mm: remove compat_process_vm_{readv,writev}")
Those commits redefined __x32_sys_* to __x64_sys_* because there is no stub
like __x32_sys_*.
Defining them as follows is more sensible and cleaner.
__SYSCALL_COMMON(nr, sym) --> __x64_<sym>
__SYSCALL_X32(nr, sym) --> __x64_<sym>
This works because both x86_64 and x32 use the same ABI (RDI, RSI, RDX,
R10, R8, R9)
The ugly #define __x32_sys_* will go away.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210517073815.97426-2-masahiroy@kernel.org
Diffstat (limited to 'arch/x86/um/sys_call_table_64.c')
0 files changed, 0 insertions, 0 deletions