Maintain consistent syscall naming across arm architecture

ARM uses unique naming conventions for certain syscalls, but
we should avoid adopting these. Specifically, fadvise64_64
will not be renamed to arm_fadvise64_64, and sync_file_range
will not be renamed to arm_sync_file_range. This ensures
uniform naming for the same syscalls across different
architectures.

Author: Cropi

lib/arm_table.h

@@ -256,7 +256,8 @@ _S(266, "statfs64")
 _S(267, "fstatfs64")
 _S(268, "tgkill")
 _S(269, "utimes")
-_S(270, "arm_fadvise64_64")
+// originally arm_fadvise64_64, but let's maintain common naming
+_S(270, "fadvise64_64")
 _S(271, "pciconfig_iobase")
 _S(272, "pciconfig_read")
 _S(273, "pciconfig_write")
@@ -327,7 +328,8 @@ _S(337, "unshare")
 _S(338, "set_robust_list")
 _S(339, "get_robust_list")
 _S(340, "splice")
-_S(341, "arm_sync_file_range")
+// originally arm_sync_file_range, but let's maintain common naming
+_S(341, "sync_file_range")
 _S(342, "tee")
 _S(343, "vmsplice")
 _S(344, "move_pages")
@@ -446,4 +448,3 @@ _S(459, "lsm_get_self_attr")
 _S(460, "lsm_set_self_attr")
 _S(461, "lsm_list_modules")
 _S(462, "mseal")
-