From: roel kluin <roel.kluin@gmail.com>
To: Raistlin <raistlin@linux.it>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
claudio@evidence.eu.com, michael@evidence.eu.com, mingo@elte.hu,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
johan.eker@ericsson.com, p.faure@akatech.ch,
Fabio Checconi <fabio@gandalf.sssup.it>,
Dhaval Giani <dhaval.giani@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
Subject: Re: [RFC][PATCH] SCHED_EDF scheduling class
Date: Tue, 29 Sep 2009 20:15:37 +0200 [thread overview]
Message-ID: <25e057c00909291115t63c36ddm657f9359d1ae34f4@mail.gmail.com> (raw)
In-Reply-To: <1253712627.5631.478.camel@Palantir>
> static int __sched_setscheduler(struct task_struct *p, int policy,
> - struct sched_param *param, bool user)
> + struct sched_param *param,
> + struct sched_param_ex *param_ex,
> + bool user)
...
> @@ -6200,6 +6364,13 @@ recheck:
> (p->mm && param->sched_priority > MAX_USER_RT_PRIO-1) ||
> (!p->mm && param->sched_priority > MAX_RT_PRIO-1))
> return -EINVAL;
> + if (edf_policy(policy) && param_ex->sched_priority != 0)
> + return -EINVAL;
> + if (edf_policy(policy) && (param_ex == NULL ||
> + timespec_to_ns(¶m_ex->sched_period) == 0 ||
> + timespec_to_ns(¶m_ex->sched_period) <
> + timespec_to_ns(¶m_ex->sched_runtime)))
> + return -EINVAL;
shouldn't the NULL test be moved upwards, to prevent a dereference of
a NULL pointer? Also I notice that `timespec_to_ns(¶m_ex->sched_period)'
is called twice, maybe gcc does this but can't we do something like
if (edf_policy(policy)) {
if (param_ex == NULL || param_ex->sched_priority != 0)
return -EINVAL;
s64 psp = timespec_to_ns(¶m_ex->sched_period);
if (psp == 0 || psp < timespec_to_ns(¶m_ex->sched_runtime))
return -EINVAL;
}
Roel
next prev parent reply other threads:[~2009-09-29 18:15 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 10:30 Raistlin
2009-09-22 11:05 ` Peter Zijlstra
2009-09-22 12:51 ` Raistlin
2009-09-22 18:36 ` Peter Zijlstra
2009-09-23 12:19 ` Raistlin
2009-09-23 12:25 ` Dhaval Giani
2009-09-27 6:55 ` Henrik Austad
2009-09-29 16:10 ` Raistlin
2009-09-29 17:34 ` Chris Friesen
2009-09-30 15:58 ` Raistlin
2009-09-30 17:35 ` Chris Friesen
2009-09-22 11:58 ` Claudio Scordino
2009-09-22 12:38 ` Peter Zijlstra
2009-09-24 16:08 ` Claudio Scordino
2009-09-22 13:24 ` Daniel Walker
2009-09-22 14:01 ` Raistlin
2009-09-22 14:02 ` Daniel Walker
2009-09-22 16:42 ` Peter Zijlstra
2009-09-22 19:11 ` Ingo Molnar
2009-09-23 0:51 ` checkpatch as a tool (was Re: [RFC][PATCH] SCHED_EDF scheduling class) Daniel Walker
2009-09-23 1:01 ` Joe Perches
2009-09-23 1:11 ` Daniel Walker
2009-09-23 19:24 ` Andy Isaacson
2009-09-24 14:58 ` Daniel Walker
2009-09-30 12:06 ` Pavel Machek
2009-09-23 12:22 ` Ingo Molnar
2009-09-23 14:43 ` Daniel Walker
2009-09-30 12:04 ` Pavel Machek
2009-09-23 7:03 ` [RFC][PATCH] SCHED_EDF scheduling class Raistlin
2009-09-23 21:39 ` Steven Rostedt
2009-09-24 0:58 ` GeunSik Lim
2009-09-22 16:38 ` Peter Zijlstra
2009-09-22 23:39 ` Jonathan Corbet
2009-09-22 23:55 ` Daniel Walker
2009-09-23 0:06 ` Jonathan Corbet
2009-09-23 0:40 ` Daniel Walker
2009-09-23 11:46 ` Avi Kivity
2009-09-23 12:25 ` Ingo Molnar
2009-09-23 14:50 ` Daniel Walker
2009-09-23 14:58 ` Avi Kivity
2009-09-23 15:08 ` Daniel Walker
2009-09-23 15:12 ` Avi Kivity
2009-09-23 15:24 ` Daniel Walker
2009-09-30 12:05 ` Pavel Machek
2009-09-22 20:55 ` Linus Walleij
2009-09-23 13:00 ` Raistlin
2009-09-23 13:22 ` Claudio Scordino
2009-09-23 14:08 ` Linus Walleij
2009-09-23 14:45 ` Raistlin
2009-09-23 12:33 ` Linus Walleij
2009-09-23 12:50 ` Linus Walleij
2009-09-23 13:30 ` Raistlin
2009-09-29 18:15 ` roel kluin [this message]
2009-09-30 15:59 ` Raistlin
2009-09-24 0:34 ` GeunSik Lim
2009-09-24 6:08 ` Raistlin
2009-09-24 9:11 ` Claudio Scordino
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=25e057c00909291115t63c36ddm657f9359d1ae34f4@mail.gmail.com \
--to=roel.kluin@gmail.com \
--cc=claudio@evidence.eu.com \
--cc=dhaval.giani@gmail.com \
--cc=fabio@gandalf.sssup.it \
--cc=johan.eker@ericsson.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@evidence.eu.com \
--cc=mingo@elte.hu \
--cc=p.faure@akatech.ch \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@sssup.it \
/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
all inboxes | Powered by JetHome®