From: Paul Jackson <pj@sgi.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: akpm@linux-foundation.org, menage@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuset: make ntasks to be a monotonic increasing value
Date: Thu, 31 Jul 2008 07:23:55 -0500 [thread overview]
Message-ID: <20080731072355.b582b2d6.pj@sgi.com> (raw)
In-Reply-To: <48912FDD.8060006@cn.fujitsu.com>
I agree that in theory, this kernel/cpuset.c update_tasks_nodemask()
loop could loop forever, and that by forcing ntasks to keep increasing
monotonically, this guarantees that it cannot loop forever.
I also agree that no known exploit of this exists, and doubt that
any could be created.
I did find the added code logic to be a tad more difficult to read
than I'd like. How about the following patch, instead:
---
kernel/cpuset.c | 3 +++
1 file changed, 3 insertions(+)
--- 2.6.25-mm1.orig/kernel/cpuset.c 2008-07-31 07:05:23.000000000 -0500
+++ 2.6.25-mm1/kernel/cpuset.c 2008-07-31 07:13:48.000000000 -0500
@@ -880,6 +880,7 @@ static int update_nodemask(struct cpuset
struct task_struct *p;
struct mm_struct **mmarray;
int i, n, ntasks;
+ int prev_ntasks = 0;
int migrate;
int fudge;
int retval;
@@ -939,7 +940,9 @@ static int update_nodemask(struct cpuset
*/
while (1) {
ntasks = cgroup_task_count(cs->css.cgroup); /* guess */
+ ntasks = max(ntasks, prev_ntasks); /* keep increasing */
ntasks += fudge;
+ prev_ntasks = ntasks;
mmarray = kmalloc(ntasks * sizeof(*mmarray), GFP_KERNEL);
if (!mmarray)
goto done;
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-07-31 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 3:22 Lai Jiangshan
2008-07-31 7:10 ` Li Zefan
2008-07-31 7:45 ` Lai Jiangshan
2008-07-31 12:23 ` Paul Jackson [this message]
2008-07-31 13:10 ` Lai Jiangshan
2008-07-31 13:37 ` Paul Jackson
2008-07-31 17:06 ` Paul Menage
2008-07-31 19:38 ` Paul Jackson
2008-07-31 20:02 ` Paul Menage
2008-08-01 1:35 ` Lai Jiangshan
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=20080731072355.b582b2d6.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome