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.
Signed-off-by: Thomas Gleixner <[email protected]> Cc: [email protected] Cc: [email protected] --- kernel/sched/core.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 1f9d6f5..3753bda 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -4441,11 +4441,13 @@ recheck: } /* - * 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 && (!rt_policy(policy) || param->sched_priority == p->rt_priority))) { - + p->sched_reset_on_fork = reset_on_fork; __task_rq_unlock(rq); raw_spin_unlock_irqrestore(&p->pi_lock, flags); return 0; -- 1.7.10.4 -- 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/
