From: Paul Mackerras <[email protected]>
Date: Thu, 8 Nov 2007 16:15:51 +1100
> David Miller writes:
>
> > I can't see where x86 is doing this though, so perhaps for x86
> > glibc does make the negative value check. But I doubt it is
> > checking the range 0x80000000-0xffffffff, otherwise mmap() would
> > be busted.
>
> At least for the INTERNAL_SYSCALL macro in glibc, the error check is:
>
> #define INTERNAL_SYSCALL_ERROR_P(val, err) \
> ((unsigned int) (val) >= 0xfffff001u)
>
> in sysdeps/unix/sysv/linux/i386/sysdep.h. Similarly the PSEUDO macro
> in that file does a cmpl $-4095,%eax to test for error. (There is also
> a PSEUDO_NOERRNO which doesn't test for error.)
>
> So the convention on (32-bit) x86 is that -4095 .. -1 are error
> values, and other values are successful return values.
Thanks for figuring that out.
Really there is no way to fix sys_times() return values
universally. Each proposed solution either doesn't fix
the problem, or adds a new failure mode.
-
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]
