linux-kernel - Re: [RFC][PATCH] lockdep: Print a nice description of an irq locking issue

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1301425790.14261.290.camel@gandalf.stny.rr.com>
Date:	Tue, 29 Mar 2011 15:09:50 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [RFC][PATCH] lockdep: Print a nice description of an irq
 locking issue

On Tue, 2011-03-29 at 20:21 +0200, Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> > 
> > > After having to explain lockdep interrupt locking inversions a few
> > > times, I decided to have lockdep spit out the scenario that it is
> > > complaining about.
> > 
> > Looks very useful!
> > 
> > Would you be interested in extending this to other lockdep splats as well? 

Sure, that should not be a problem.

> 
> In separate patches, of course.

Of course ;)

-- Steve


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