[RFC] sys_setrlimit() in 2.6.16
- From: Cliff Wickman <cpw@xxxxxxx>
- Date: Tue, 14 Feb 2006 16:24:17 -0600
A test suite uncovered a possible bug in setrlimit(2), in 2.6.16-rc3.
A code that does
mylimits.rlim_cur = 0;
setrlimit(RLIMIT_CPU, &mylimits);
does not set a cpu time limit.
No signal is sent to this code when its "limit" of 0 seconds expires.
Whereas, under the 2.6.5 kernel (SuSE SLESS9) a signal was sent.
I don't see any obvious difference in sys_setrlimit() or
set_process_cpu_timer() between 2.6.5 and 2.6.16.
Is this a correction, or a bug?
Is a cpu time limit of 0 supposed to limit a task to 0 seconds, or
leave it unlimited?
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@xxxxxxx
(651) 683-3824
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC] sys_setrlimit() in 2.6.16
- From: Andrew Morton
- Re: [RFC] sys_setrlimit() in 2.6.16
- Prev by Date: Re: Random reboots
- Next by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
- Previous by thread: bonding mode 1 works as designed. Or not?
- Next by thread: Re: [RFC] sys_setrlimit() in 2.6.16
- Index(es):
Relevant Pages
|
