From: Thomas Gleixner <[email protected]> If the policy and priority remain unchanged a possible modification of sched_reset_on_fork gets lost in the early exit path.
Cc: [email protected] Signed-off-by: Thomas Gleixner <[email protected]> [bigeasy: rebase ontop of v3.14-rc1] Signed-off-by: Sebastian Andrzej Siewior <[email protected]> --- kernel/sched/core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 3112b28..a4c06a8 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -3392,7 +3392,8 @@ static int __sched_setscheduler(struct task_struct *p, } /* - * If not changing anything there's no need to proceed further: + * If not changing anything there's no need to proceed further, + * but store a possible modification of reset_on_fork. */ if (unlikely(policy == p->policy)) { if (fair_policy(policy) && attr->sched_nice != TASK_NICE(p)) @@ -3402,6 +3403,7 @@ static int __sched_setscheduler(struct task_struct *p, if (dl_policy(policy)) goto change; + p->sched_reset_on_fork = reset_on_fork; task_rq_unlock(rq, p, &flags); return 0; } -- 1.9.rc1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
