Arnd Bergmann 54233a4254 uretprobe: change syscall number, again ... Despite multiple attempts to get the syscall number assignment right for the newly added uretprobe syscall, we ended up with a bit of a mess: - The number is defined as 467 based on the assumption that the xattrat family of syscalls would use 463 through 466, but those did not make it into 6.11. - The include/uapi/asm-generic/unistd.h file still lists the number 463, but the new scripts/syscall.tbl that was supposed to have the same data lists 467 instead as the number for arc, arm64, csky, hexagon, loongarch, nios2, openrisc and riscv. None of these architectures actually provide a uretprobe syscall. - All the other architectures (powerpc, arm, mips, ...) don't list this syscall at all. There are two ways to make it consistent again: either list it with the same syscall number on all architectures, or only list it on x86 but not in scripts/syscall.tbl and asm-generic/unistd.h. Based on the most recent discussion, it seems like we won't need it anywhere else, so just remove the inconsistent assignment and instead move the x86 number to the next available one in the architecture specific range, which is 335. Fixes: 5c28424e9a ("syscalls: Fix to add sys_uretprobe to syscall.tbl") Fixes: 190fec72df ("uprobe: Wire up uretprobe system call") Fixes: 63ded11097 ("uprobe: Change uretprobe syscall scope and number") Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Reviewed-by: Jiri Olsa <jolsa@kernel.org> Signed-off-by: Arnd Bergmann <arnd@arndb.de>		2024-08-02 15:18:49 +02:00
..
Makefile	Kbuild updates for v5.18	2022-03-31 11:59:03 -07:00
syscall_32.tbl	- Add a spectre_bhi=vmexit mitigation option aimed at cloud	2024-07-15 20:07:27 -07:00
syscall_64.tbl	uretprobe: change syscall number, again	2024-08-02 15:18:49 +02:00