summaryrefslogtreecommitdiffstats
path: root/kernel/acct.c
diff options
context:
space:
mode:
authorAndrew Morton <akpm@osdl.org>2006-03-24 12:18:35 +0100
committerLinus Torvalds <torvalds@g5.osdl.org>2006-03-24 16:33:30 +0100
commite0661111e5441995f7a69dc4336c9f131cb9bc58 (patch)
tree47a0a0ae66a9f792e6c9edbf683cdc0b62a2d4b7 /kernel/acct.c
parent[PATCH] sys_setrlimit() cleanup (diff)
downloadlinux-e0661111e5441995f7a69dc4336c9f131cb9bc58.tar.xz
linux-e0661111e5441995f7a69dc4336c9f131cb9bc58.zip
[PATCH] RLIMIT_CPU: fix handling of a zero limit
At present the kernel doesn't honour an attempt to set RLIMIT_CPU to zero seconds. But the spec says it should, and that's what 2.4.x does. Fixing this for real would involve some complexity (such as adding a new it-has-been-set flag to the task_struct, and testing that everwhere, instead of overloading the value of it_prof_expires). Given that a 2.4 kernel won't actually send the signal until one second has expired anyway, let's just handle this case by treating the caller's zero-seconds as one second. Cc: Martin Schwidefsky <schwidefsky@de.ibm.com> Cc: Ulrich Weigand <uweigand@de.ibm.com> Cc: Cliff Wickman <cpw@sgi.com> Acked-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel/acct.c')
0 files changed, 0 insertions, 0 deletions