From: Andrew Morton <[email protected]>
Date: Wed, 7 Nov 2007 15:28:33 -0800
> Perhaps this is a bug in glibc: it is interpreting the times() return value
> in the same way as other syscalls.
The problem is more likely that we are failing to
invoke force_successful_syscall_return() here.
Otherwise the syscall return path interprets negative
values as errors, and sets the cpu condition codes.
And that is what userspace is actually checking for
to determine if there is an error or not.
-
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]
