Subject: Re: [patch] Re: [regression bisect -next] BUG: using
 smp_processor_id() in preemptible [00000000] code: rmmod
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Eric Paris <eparis@redhat.com>, linux-kernel@vger.kernel.org,
       hpa@zytor.com, a.p.zijlstra@chello.nl, tglx@linutronix.de
In-Reply-To: <20091029091411.GE22963@elte.hu>
References: <1256784158.2848.8.camel@dhcp231-106.rdu.redhat.com>
	 <1256805552.7158.22.camel@marge.simson.net>
	 <20091029091411.GE22963@elte.hu>
Content-Type: text/plain
Date: Thu, 29 Oct 2009 10:19:27 +0100
Message-Id: <1256807967.7158.58.camel@marge.simson.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 739
Lines: 18

On Thu, 2009-10-29 at 10:14 +0100, Ingo Molnar wrote:

> hm, the problem is kthread_bind(). It is rummaging around in scheduler 
> internals without holding the runqueue lock - and this now got exposed. 
> Even though it is operating on (supposedly ...) inactive tasks, the guts 
> of that function should be moved into sched.c and it should be fixed to 
> have proper locking.

Yeah, I was thinking that nobody should ever be able to hit that without
it being a bug.. but wimped out.

	-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/