[lkml]   [2007]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: compat_sys_times() bogus until jiffies >= 0.
    From: Andrew Morton <>
    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
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-11-08 04:17    [W:0.019 / U:308.980 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site