x86/syscalls: Document the fact that syscalls 512-547 are a legacy mistake
authorAndy Lutomirski <luto@kernel.org>
Mon, 12 Oct 2020 02:51:21 +0000 (19:51 -0700)
committerIngo Molnar <mingo@kernel.org>
Wed, 14 Oct 2020 17:53:40 +0000 (19:53 +0200)
commitc3b484c439b0bab7a698495f33ef16286a1000c4
treebebb383c2c784e27f24861b1173bc975e5876c90
parentf2ac57a4c49d40409c21c82d23b5706df9b438af
x86/syscalls: Document the fact that syscalls 512-547 are a legacy mistake

Since this commit:

  6365b842aae4 ("x86/syscalls: Split the x32 syscalls into their own table")

there is no need for special x32-specific syscall numbers.  I forgot to
update the comments in syscall_64.tbl.  Add comments to make it clear to
future contributors that this range is a legacy wart.

Reported-by: Jessica Clarke <jrtc27@jrtc27.com>
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/6c56fb4ddd18fc60a238eb4d867e4b3d97c6351e.1602471055.git.luto@kernel.org
arch/x86/entry/syscalls/syscall_64.tbl