Balbir Singh 49048622ea sched: fix process time monotonicity
Spencer reported a problem where utime and stime were going negative despite
the fixes in commit b27f03d4bdc145a09fb7b0c0e004b29f1ee555fa. The suspected
reason for the problem is that signal_struct maintains it's own utime and
stime (of exited tasks), these are not updated using the new task_utime()
routine, hence sig->utime can go backwards and cause the same problem
to occur (sig->utime, adds tsk->utime and not task_utime()). This patch
fixes the problem

TODO: using max(task->prev_utime, derived utime) works for now, but a more
generic solution is to implement cputime_max() and use the cputime_gt()
function for comparison.

Reported-by: spencer@bluehost.com
Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-09-05 18:14:35 +02:00
..
2008-09-05 18:14:35 +02:00
2008-08-05 14:33:50 -07:00
2008-08-25 01:18:03 -04:00
2005-04-16 15:20:36 -07:00
2008-07-26 20:53:12 -04:00
2008-07-25 10:53:44 -07:00
2008-07-25 10:53:45 -07:00
2007-10-17 08:42:48 -07:00
2008-07-22 14:19:19 -07:00
2008-07-20 17:12:34 -07:00