arm64: seccomp: fix the incorrect name of syscall __NR_compat_exit in secure computing mode

hulk inclusion
category: bugfix
bugzilla: 176178 https://gitee.com/openeuler/kernel/issues/I4DDEL

--------

In secure computing mode, due to the incorrect name of syscall
__NR_compat_exit, while setting as strict mode, calling exit(0) will return
SIGKILL, which does not match our expectation. This patch fixes it.

Fixes: 2227c11c5f07 ("[Huawei] arm64: secomp: fix the secure computing mode 1 syscall check for ilp32")
Signed-off-by: NChen Jiahao <chenjiahao16@huawei.com>
Reviewed-by: NLiao Chang <liaochang1@huawei.com>
Signed-off-by: NChen Jun <chenjun102@huawei.com>
Signed-off-by: NZheng Zengkai <zhengzengkai@huawei.com>

arch/arm64/include/asm/seccomp.h

@@ -25,7 +25,7 @@ static inline const int *get_compat_mode1_syscalls(void)
 #ifdef CONFIG_AARCH32_EL0
 	static const int mode1_syscalls_a32[] = {
 		__NR_compat_read, __NR_compat_write,
-		__NR_compat_read, __NR_compat_sigreturn,
+		__NR_compat_exit, __NR_compat_sigreturn,
 		0, /* null terminated */
 	};
 #endif