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: <20110715220447.GJ2327@linux.vnet.ibm.com>
Date:	Fri, 15 Jul 2011 15:04:47 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Ed Tomlinson <edt@....ca>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dipankar Sarma <dipankar@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: INFO: possible circular locking dependency detected

On Fri, Jul 15, 2011 at 05:48:06PM -0400, Ed Tomlinson wrote:
> On Friday 15 July 2011 12:56:13 Paul E. McKenney wrote:

[ . . . ]

> > OK.  Ed, would you be willing to try the patch out?
> 
> I am booted at the same git commit with a bluetooth and the disable local_bh around softirq()
> patch from this thread.  So far so good.  Not sure how 'easy' this one is to trigger a second time -
> I've been running with threadirq enabled since .39 came out.  Last night was the first deadlock...
> If nothing happened post rc6 to make it more likely it could be a while before it triggers again.

Thank you for trying it out, Ed!  And I know that you will not be shy
should the problem recur.  ;-)

							Thanx, Paul
--
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/