On Monday 2009-12-14 04:25, David Miller wrote: > >cp_new_stat() handles "struct stat", not "struct stat64" > >cp_new_stat64() does that, and it unconditionally fills in >the nsec parts. I added some dump_stack() to all the cp_* functions, leading to this result: Call Trace: [0000000000522990] cp_new_stat+0xdc/0x134 [0000000000522d9c] SyS_newfstat+0x24/0x38 [0000000000406294] linux_sparc_syscall+0x34/0x44 Is glibc doing the right thing here? Calling sys_newfstat (instead of sys_newfstat64) for fstat64()? [gcc-bug: see http://marc.info/?l=linux-sparc&m=126074570109411&w=2 ] -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
