From: Ingo Molnar <mingo@elte.hu>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, drepper@redhat.com,
Tony.Reix@bull.net, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [2.6 patch] fix sched_setscheduler semantics
Date: Tue, 17 Jan 2006 08:59:24 +0100 [thread overview]
Message-ID: <20060117075924.GC13580@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0601161650540.21530@dhcp83-105.boston.redhat.com>
* Jason Baron <jbaron@redhat.com> wrote:
> Therefore, i'd suggest the following patch. Verified to fix the
> attached test case. Thanks to Tony Reix for pointing this out.
indeed - good catch.
> asmlinkage long sys_sched_setscheduler(pid_t pid, int policy,
> struct sched_param __user *param)
> {
> + /* negative values for policy are not valid */
> + if (policy < 0)
> + return -EINVAL;
> +
> return do_sched_setscheduler(pid, policy, param);
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
prev parent reply other threads:[~2006-01-17 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 22:17 Jason Baron
2006-01-16 22:52 ` Alexey Dobriyan
2006-01-16 22:57 ` Alan Cox
2006-01-17 7:59 ` Ingo Molnar [this message]
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=20060117075924.GC13580@elte.hu \
--to=mingo@elte.hu \
--cc=Tony.Reix@bull.net \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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®