* Question: possible bug in setrlimit
@ 2006-02-13 23:00 Cliff Wickman
0 siblings, 0 replies; only message in thread
From: Cliff Wickman @ 2006-02-13 23:00 UTC (permalink / raw)
To: linux-kernel
A test suite uncovered a possible bug in setrlimit(2).
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.
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 a cpu time limit of 0 supposed to limit to 0 seconds, or be unlimited?
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-02-13 23:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-13 23:00 Question: possible bug in setrlimit Cliff Wickman
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.