linux-kernel - Re: INFO: possible circular locking dependency detected

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1310661699.2309.13.camel@laptop>
Date:	Thu, 14 Jul 2011 18:41:39 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Dipankar Sarma <dipankar@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: INFO: possible circular locking dependency detected

On Thu, 2011-07-14 at 17:49 +0300, Sergey Senozhatsky wrote:
> Hello,
> 
> [ 4172.371094] =======================================================
> [ 4172.371097] [ INFO: possible circular locking dependency detected ]
> [ 4172.371103] 3.0.0-rc7-dbg-00565-g6b31efc #644
> [ 4172.371105] -------------------------------------------------------
> [ 4172.371108] make/11702 is trying to acquire lock:
> [ 4172.371111]  (rcu_node_level_0){..-...}, at: [<ffffffff810a55e2>] __rcu_read_unlock+0xb9/0x217
> [ 4172.371123] 
> [ 4172.371123] but task is already holding lock:
> [ 4172.371125]  (&p->pi_lock){-.-.-.}, at: [<ffffffff8103775e>] try_to_wake_up+0x29/0x28b
> [ 4172.371135] 
> [ 4172.371135] which lock already depends on the new lock.

Happen to have a .config and means of reproduction? We're a little
stumped at trying to explain how this can actually happen.



--
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/