From: Andrew Morton <[email protected]>
Date: Wed, 7 Nov 2007 19:07:14 -0800
> It appears that glibc treats all of 0x80000000-0xffffffff as an
> error.
glibc treats it as an error if the system call returns with
the carry condition code set. At least that's how I've
understood it to work and at a minimum this is how it works
on sparc, ppc, ia64, mips, etc.
The error indication is being created by the system call return path
in the kernel. It tests for values between -512 and 0, and marks
those as errors unless force_successful_syscall() has been called.
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.
-
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]
