This is a note to let you know that I've just added the patch titled

    sched: Fix sched_setparam() policy == -1 logic

to the 3.14-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     sched-fix-sched_setparam-policy-1-logic.patch
and it can be found in the queue-3.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From d8d28c8f00e84a72e8bee39a85835635417bee49 Mon Sep 17 00:00:00 2001
From: Daniel Bristot de Oliveira <[email protected]>
Date: Tue, 22 Jul 2014 23:27:41 -0300
Subject: sched: Fix sched_setparam() policy == -1 logic

From: Daniel Bristot de Oliveira <[email protected]>

commit d8d28c8f00e84a72e8bee39a85835635417bee49 upstream.

The scheduler uses policy == -1 to preserve the current policy state to
implement sched_setparam(). But, as (int) -1 is equals to 0xffffffff,
it's matching the if (policy & SCHED_RESET_ON_FORK) on
_sched_setscheduler(). This match changes the policy value to an
invalid value, breaking the sched_setparam() syscall.

This patch checks policy == -1 before check the SCHED_RESET_ON_FORK flag.

The following program shows the bug:

int main(void)
{
        struct sched_param param = {
                .sched_priority = 5,
        };

        sched_setscheduler(0, SCHED_FIFO, &param);
        param.sched_priority = 1;
        sched_setparam(0, &param);
        param.sched_priority = 0;
        sched_getparam(0, &param);
        if (param.sched_priority != 1)
                printf("failed priority setting (found %d instead of 1)\n",
                        param.sched_priority);
        else
                printf("priority setting fine\n");
}

Signed-off-by: Daniel Bristot de Oliveira <[email protected]>
Signed-off-by: Peter Zijlstra <[email protected]>
Reviewed-by: Steven Rostedt <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: [email protected]
Fixes: 7479f3c9cf67 "sched: Move SCHED_RESET_ON_FORK into attr::sched_flags"
Link: 
http://lkml.kernel.org/r/9ebe0566a08dbbb3999759d3f20d6004bb2dbcfa.1406079891.git.bris...@redhat.com
Signed-off-by: Ingo Molnar <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 kernel/sched/core.c |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3511,9 +3511,10 @@ static int _sched_setscheduler(struct ta
        };
 
        /*
-        * Fixup the legacy SCHED_RESET_ON_FORK hack
+        * Fixup the legacy SCHED_RESET_ON_FORK hack, except if
+        * the policy=-1 was passed by sched_setparam().
         */
-       if (policy & SCHED_RESET_ON_FORK) {
+       if ((policy != -1) && (policy & SCHED_RESET_ON_FORK)) {
                attr.sched_flags |= SCHED_FLAG_RESET_ON_FORK;
                policy &= ~SCHED_RESET_ON_FORK;
                attr.sched_policy = policy;


Patches currently in stable-queue which might be from [email protected] are

queue-3.14/sched-fix-sched_setparam-policy-1-logic.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to