public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] sched: fix broken SCHED_RESET_ON_FORK handling
Date: Wed, 27 Jul 2011 18:10:35 +0200	[thread overview]
Message-ID: <1311783035.10246.1.camel@marge.simson.net> (raw)
In-Reply-To: <1311779695.8691.2.camel@marge.simson.net>

I knew that thing had been moved before.. see f83f9ac2.

On Wed, 2011-07-27 at 17:14 +0200, Mike Galbraith wrote:
> sched: fix broken SCHED_RESET_ON_FORK handling
> 
> Setting child->prio = current->normal_prio _after_ SCHED_RESET_ON_FORK has
> been handled for an RT parent gives birth to a deranged mutant child with
> non-RT policy, but RT prio and sched_class.
> 
> Move PI leakage protection up, always set priorities and weight, and if the
> child is leaving RT class, reset rt_priority to the proper value.
> 
> Signed-off-by: Mike Galbraith <efault@gmx.de>
> Cc: <stable@kernel.org>
> 
> diff --git a/kernel/sched.c b/kernel/sched.c
> index 0281f84..a3e65a0 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -2804,19 +2804,23 @@ void sched_fork(struct task_struct *p)
>  	p->state = TASK_RUNNING;
>  
>  	/*
> +	 * Make sure we do not leak PI boosting priority to the child.
> +	 */
> +	p->prio = current->normal_prio;
> +
> +	/*
>  	 * Revert to default priority/policy on fork if requested.
>  	 */
>  	if (unlikely(p->sched_reset_on_fork)) {
> -		if (p->policy == SCHED_FIFO || p->policy == SCHED_RR) {
> +		if (task_has_rt_policy(p)) {
>  			p->policy = SCHED_NORMAL;
> -			p->normal_prio = p->static_prio;
> -		}
> -
> -		if (PRIO_TO_NICE(p->static_prio) < 0) {
>  			p->static_prio = NICE_TO_PRIO(0);
> -			p->normal_prio = p->static_prio;
> -			set_load_weight(p);
> -		}
> +			p->rt_priority = 0;
> +		} else if (PRIO_TO_NICE(p->static_prio) < 0)
> +			p->static_prio = NICE_TO_PRIO(0);
> +
> +		p->prio = p->normal_prio = __normal_prio(p);
> +		set_load_weight(p);
>  
>  		/*
>  		 * We don't need the reset flag anymore after the fork. It has
> @@ -2825,11 +2829,6 @@ void sched_fork(struct task_struct *p)
>  		p->sched_reset_on_fork = 0;
>  	}
>  
> -	/*
> -	 * Make sure we do not leak PI boosting priority to the child.
> -	 */
> -	p->prio = current->normal_prio;
> -
>  	if (!rt_prio(p->prio))
>  		p->sched_class = &fair_sched_class;
>  
> 
> 



  reply	other threads:[~2011-07-27 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 15:14 [patch] sched: fix broken SCHED_RESET_ON_FORK handling Mike Galbraith
2011-07-27 16:10 ` Mike Galbraith [this message]
2011-08-14 15:58 ` [tip:sched/core] " tip-bot for Mike Galbraith

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=1311783035.10246.1.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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