mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <bitbucket@online.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.9-rt21
Date: Mon, 17 Dec 2012 18:09:36 +0100	[thread overview]
Message-ID: <1355764176.11540.19.camel@marge.simpson.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1212171634070.3148@ionos>

On Mon, 2012-12-17 at 16:35 +0100, Thomas Gleixner wrote: 
> On Sat, 15 Dec 2012, Mike Galbraith wrote:
> > On Wed, 2012-12-05 at 17:05 +0100, Thomas Gleixner wrote: 
> > > Dear RT Folks,
> > > 
> > > I'm pleased to announce the 3.6.9-rt21 release. 3.6.7-rt18, 3.6.8-rt19
> > > and 3.6.9-rt20 are not announced updates to the respective 3.6.y
> > > stable releases without any RT changes
> > > 
> > > Changes since 3.6.9-rt20:
> > > 
> > >    * Fix the PREEMPT_LAZY implementation on ARM
> > > 
> > >    * Fix the RCUTINY issues
> > > 
> > >    * Fix a long standing scheduler bug (See commit log of
> > >      sched-enqueue-to-head.patch)
> > 
> > That last has an oversight buglet.
> > 
> > sched: add missing userspace->kernel struct sched_param.sched_priority inversion
> > 
> > Signed-off-by: Mike Galbraith <bitbucket@online.de>
> > ---
> >  kernel/sched/core.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -4624,7 +4624,7 @@ static int __sched_setscheduler(struct t
> >  	p->sched_reset_on_fork = reset_on_fork;
> >  
> >  	oldprio = p->prio;
> > -	if (oldprio == param->sched_priority)
> > +	if (oldprio == (MAX_RT_PRIO - 1) - param->sched_priority)
> >  		goto out;
> >  
> >  	on_rq = p->on_rq;
> 
> Duh, yes. But there is another one here:
> 
> +               enqueue_task(rq, p, oldprio < param->sched_priority ?
> +                            ENQUEUE_HEAD : 0);
> 
> Bah. This reverse user/kernel priority nonsense really should go away!

Snort, I looked right at it too, looked perfectly fine :)

-Mike


  reply	other threads:[~2012-12-17 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 16:05 Thomas Gleixner
2012-12-06 14:35 ` Tim Sander
2012-12-06 20:52   ` Tim Sander
2012-12-09  0:48   ` Ove Karlsen
     [not found]     ` <50C3DB17.2010705@earthlink.net>
2012-12-09 10:08       ` Ove Karlsen
2012-12-15  3:52 ` Mike Galbraith
2012-12-17 15:35   ` Thomas Gleixner
2012-12-17 17:09     ` Mike Galbraith [this message]
2012-12-17 19:44       ` Thomas Gleixner

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=1355764176.11540.19.camel@marge.simpson.net \
    --to=bitbucket@online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome