Balbir Singh 49048622ea sched: fix process time monotonicity ... Spencer reported a problem where utime and stime were going negative despite the fixes in commit b27f03d4bd. 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
..
array.c	sched: fix process time monotonicity	2008-09-05 18:14:35 +02:00
base.c
generic.c
inode-alloc.txt
inode.c
internal.h
Kconfig
kcore.c
kmsg.c
Makefile
mmu.c
nommu.c
proc_devtree.c
proc_misc.c
proc_net.c
proc_sysctl.c
proc_tty.c
root.c
task_mmu.c
task_nommu.c
vmcore.c