Commit 63415dbb authored by Richard Sandiford's avatar Richard Sandiford Committed by Ralf Baechle

[MIPS] The o32 fstatat syscall behaves differently on 32 and 64 bit kernels

While working on a glibc patch to support the fstatat() functions[1],
I noticed that the o32 implementation behaves differently on 32-bit and
64-bit kernels; the former provides a stat64 while the latter provides
a plain (o32) stat.  I think the former is what's intended, as there is
no separate fstatat64.  It's also what x86 does.

I think this is just a case of a compat too far.

[1] I've seen Khem's patch, but I don't think it's right.
Signed-off-by: default avatarRichard Sandiford <richard@codesourcery.com>
Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
parent d48f1de2
...@@ -498,7 +498,7 @@ sys_call_table: ...@@ -498,7 +498,7 @@ sys_call_table:
PTR sys_mknodat /* 4290 */ PTR sys_mknodat /* 4290 */
PTR sys_fchownat PTR sys_fchownat
PTR compat_sys_futimesat PTR compat_sys_futimesat
PTR compat_sys_newfstatat PTR sys_newfstatat
PTR sys_unlinkat PTR sys_unlinkat
PTR sys_renameat /* 4295 */ PTR sys_renameat /* 4295 */
PTR sys_linkat PTR sys_linkat
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment