Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756194AbZKIPqL (ORCPT ); Mon, 9 Nov 2009 10:46:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756153AbZKIPqK (ORCPT ); Mon, 9 Nov 2009 10:46:10 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:48955 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756149AbZKIPqJ (ORCPT ); Mon, 9 Nov 2009 10:46:09 -0500 Date: Mon, 9 Nov 2009 16:45:27 +0100 From: Ingo Molnar To: Jens Axboe Cc: Tejun Heo , Jiri Kosina , Peter Zijlstra , Yinghai Lu , Thomas Gleixner , cl@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: irq lock inversion Message-ID: <20091109154527.GA24969@elte.hu> References: <86802c440911041008q4969b9bdk15b4598c40bb84bd@mail.gmail.com> <4AF25FC7.4000502@kernel.org> <20091105082102.GA2870@elte.hu> <4AF28D7A.6020209@kernel.org> <4AF3B9BD.9050300@kernel.org> <20091106071711.GA20946@elte.hu> <20091106095922.GH8742@kernel.dk> <20091108093859.GA2845@elte.hu> <20091109153418.GX8742@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091109153418.GX8742@kernel.dk> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1662 Lines: 41 * Jens Axboe wrote: > On Sun, Nov 08 2009, Ingo Molnar wrote: > > > > * Jens Axboe wrote: > > > > > On Fri, Nov 06 2009, Ingo Molnar wrote: > > > > Read the lockdep message please, consider all the backtraces it prints, > > > > it says something different. > > > > > > In all honesty, reading and parsing lockdep messages requires a > > > special state of mind. IOW, readability is not its high point. > > > > We frequently do patches to improve the messages but there's a hard > > limit: generally the messages mirror the complexity of the underlying > > locking scenario. > > > > Unfortunately lockdep cannot pretend something is simple when it is not. > > There are two ways out of that: either to simplify the underlying > > locking rules, or to understand them. > > I think the primary problem is that it tries to condense too much > information, instead of just spelling it out. That may be obvious to a > person intimately familiar with lockdep, but not to others. Things > like the STATE line, for instance. It would read a lot easier if these > things were just spelled out. > > I know this message isn't really productive, just tossing it out > there. I'll try to to back it up with a patch the next time it annoys > me :-) Well, previously lockdep spewed out a lot of info, which we condensed down because people complained ;-) Ingo -- 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/