x86/entry/x32: Rename __x32_compat_sys_* to __x64_compat_sys_*
authorMasahiro Yamada <masahiroy@kernel.org>
Mon, 17 May 2021 07:38:09 +0000 (16:38 +0900)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 20 May 2021 13:03:58 +0000 (15:03 +0200)
commit2e958a8a510d956ec8528f0bd20e309b5bb5156c
tree57661eec425dbdb46c183f12a7f1ae21fa95ed09
parent41f45fb045bcc20e71eb705b361356e715682162
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
arch/x86/entry/syscall_x32.c
arch/x86/include/asm/syscall_wrapper.h