From: Cliff Wickman <cpw@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Question: possible bug in setrlimit
Date: Mon, 13 Feb 2006 17:00:51 -0600 [thread overview]
Message-ID: <20060213230051.GA29417@sgi.com> (raw)
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
reply other threads:[~2006-02-13 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060213230051.GA29417@sgi.com \
--to=cpw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.