> --- linux-2.6.15.i686/arch/i386/kernel/syscall_table.S-at 2006-02-06 13:11:24.000000000 -0800
> +++ linux-2.6.15.i686/arch/i386/kernel/syscall_table.S 2006-02-06 13:11:34.000000000 -0800
> @@ -299,7 +299,7 @@
> .long sys_mknodat
> .long sys_fchownat
> .long sys_futimesat
> - .long sys_newfstatat /* 300 */
> + .long sys_fstatat64 /* 300 */
> .long sys_unlinkat
> .long sys_renameat
> .long sys_linkat
> --- linux-2.6.15.i686/arch/x86_64/ia32/ia32entry.S-at 2006-02-06 13:05:04.000000000 -0800
> +++ linux-2.6.15.i686/arch/x86_64/ia32/ia32entry.S 2006-02-06 13:05:21.000000000 -0800
> @@ -677,7 +677,7 @@
> .quad sys_mknodat
> .quad sys_fchownat
> .quad compat_sys_futimesat
> - .quad compat_sys_newfstatat /* 300 */
> + .quad sys32_fstatat /* 300 */
> .quad sys_unlinkat
> .quad sys_renameat
> .quad sys_linkat
So we end up with sys_newfstatat for 64 bit architectures, sys_fstatat64
for 32 bit architectures and sys32_fstatat for compat mode. Shouldn't the
name of the compat call changed to sys32_fstatat64?
At least that is how it used to be for all other *64 compat system calls
like e.g. fstat64.
Heiko
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
