All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Langsdorf, Mark" <mark.langsdorf@amd.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Gautham R Shenoy <ego@in.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Regression in 2.6.27-rc1 for set_cpus_allowed_ptr
Date: Tue, 12 Aug 2008 00:10:41 +0200	[thread overview]
Message-ID: <20080811221041.GA17634@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0808111500330.3462@nehalem.linux-foundation.org>

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Mon, 11 Aug 2008, Ingo Molnar wrote:
> > 
> > i've queued up the fix below in tip/sched/urgent.
> > 
> > diff --git a/kernel/cpu.c b/kernel/cpu.c
> > index e202a68..c977c33 100644
> > --- a/kernel/cpu.c
> > +++ b/kernel/cpu.c
> > @@ -349,6 +349,8 @@ static int __cpuinit _cpu_up(unsigned int cpu, int tasks_frozen)
> >  		goto out_notify;
> >  	BUG_ON(!cpu_online(cpu));
> >  
> > +	cpu_set(cpu, cpu_active_map);
> > +
> >  	/* Now call notifier in preparation. */
> >  	raw_notifier_call_chain(&cpu_chain, CPU_ONLINE | mod, hcpu);
> >  
> > @@ -383,9 +385,6 @@ int __cpuinit cpu_up(unsigned int cpu)
> >  
> >  	err = _cpu_up(cpu, 0);
> >  
> > -	if (cpu_online(cpu))
> > -		cpu_set(cpu, cpu_active_map);
> > -
> 
> Ok, not only does that fix the bug, but it simplifies the code and 
> looks obviously ok. However, I don't have it in my tree yet, and I'd 
> like to do an -rc3 that has this fixes (so that along with the PCI MSI 
> thing, we hopefully have most of the suspend/resume regressions 
> fixed).
> 
> And I was hoping to do -rc3 today. Can I please have pull-requests for 
> the appropriate urgent scheduler/x86 fixes? Or should I just take 
> these as patches?

i'll send pull requests for all pending patches. I wanted to send them 
tomorrow originally but will do them now.

	Ingo

  reply	other threads:[~2008-08-11 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 19:44 Regression in 2.6.27-rc1 for set_cpus_allowed_ptr Langsdorf, Mark
2008-08-08 21:03 ` Rafael J. Wysocki
2008-08-08 21:31   ` Dmitry Adamushko
2008-08-11 12:30     ` Ingo Molnar
2008-08-11 14:01       ` Langsdorf, Mark
2008-08-11 14:20         ` Ingo Molnar
2008-08-11 14:28       ` Dmitry Adamushko
2008-08-11 22:03       ` Linus Torvalds
2008-08-11 22:10         ` Ingo Molnar [this message]
2008-08-11 22:14         ` Max Krasnyansky
2008-08-11 22:46           ` Ingo Molnar
2008-08-11 22:49             ` Max Krasnyansky
2008-08-11 22:55               ` Ingo Molnar

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=20080811221041.GA17634@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.adamushko@gmail.com \
    --cc=ego@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.