linux-kernel - Re: BUG: spinlock lockup on task_rq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 2 Mar 2010 23:49:43 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Dave Chinner <david@...morbit.com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: BUG: spinlock lockup on task_rq_lock in 2.6.33

On Wed, 3 Mar 2010, Dave Chinner wrote:
> On Tue, Mar 02, 2010 at 11:08:50AM +0100, Thomas Gleixner wrote:
> > Dave,
> > 
> > On Tue, 2 Mar 2010, Dave Chinner wrote:
> > 
> > > Hi Folks,
> > > 
> > > I just locked up a machine with the following trace:
> > > 
> > > [ 5247.149256] BUG: spinlock lockup on CPU#1, dd/7018, ffff8800059d4380
> > > [ 5247.150009] BUG: spinlock lockup on CPU#0, dd/6211, ffff8800059d4380
> > > [ 5247.150009] Pid: 6211, comm: dd Not tainted 2.6.33-dgc #86
> > > [ 5247.150009] Call Trace:
> > > [ 5247.150009]  [<ffffffff8140ad40>] do_raw_spin_lock+0x160/0x170
> > > [ 5247.150009]  [<ffffffff8170fec6>] _raw_spin_lock+0x56/0x70
> > > [ 5247.150009]  [<ffffffff8103d092>] ? task_rq_lock+0x52/0x90
> > > [ 5247.150009]  [<ffffffff8103d092>] task_rq_lock+0x52/0x90
> > > [ 5247.150009]  [<ffffffff81044a70>] try_to_wake_up+0x40/0x3d0
> > > [ 5247.150009]  [<ffffffff81044e55>] wake_up_process+0x15/0x20
> > 
> > I can't say it for sure, but that might be related to a problem with
> > TASK_WAKING which we discovered recently. The fix is in linus tree
> > (commit 0970d2992dfd7d5ec2c787417cf464f01eeaf42a) and on the way to stable.
> 
> Thanks Thomas - I'll pull that commit in and see if it has any
> effect on the problems I'm seeing.

I have a hard time to see how that might lead to a deadlock, but hell,
that load balancing code is a maze.

Thanks,

	tglx

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