This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/1176] New: sys_times return value
- From: "navlrac at hotmail dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 5 Aug 2005 13:06:57 -0000
- Subject: [Bug libc/1176] New: sys_times return value
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
Quoting Russell King's explaination of original bug I filed.
ARM folk have recently pointed out a problem with sys_times().
When the kernel (2.6) boots, we set jiffies to -5 minutes. This causes
sys_times() to return a negative number, which increments through
zero.
However, some negative numbers are used to return error codes.
Hence, there's a period of time when sys_times() returns values
which are indistinguishable from error codes shortly after boot.
This probably only affects 32-bit architectures. However, one
wonders whether sys_times() needs force_successful_syscall_return().
Also, it appears that glibc does indeed interpret the return value
from sys_times in the way I describe above on at least ARM and x86.
Other architectures may be similarly affected.
--
Summary: sys_times return value
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: navlrac at hotmail dot com
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: arm-linux-gnu
GCC host triplet: i386-linux-gnu
GCC target triplet: arm-linux-gnu
http://sources.redhat.com/bugzilla/show_bug.cgi?id=1176
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.