From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753911Ab1C2Txd (ORCPT ); Tue, 29 Mar 2011 15:53:33 -0400 Received: from www.linutronix.de ([62.245.132.108]:45428 "EHLO linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750942Ab1C2Txc (ORCPT ); Tue, 29 Mar 2011 15:53:32 -0400 Date: Tue, 29 Mar 2011 21:53:29 +0200 (CEST) From: Thomas Gleixner To: Steven Rostedt cc: LKML , Ingo Molnar , Andrew Morton , Linus Torvalds , Peter Zijlstra Subject: Re: [RFC][PATCH] lockdep: Print a nice description of an irq locking issue In-Reply-To: <1301418845.14261.284.camel@gandalf.stny.rr.com> Message-ID: References: <1301418845.14261.284.camel@gandalf.stny.rr.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 29 Mar 2011, Steven Rostedt wrote: > other info that might help us debug this: > > Chain exists of: > &rq->lock --> lockA --> lockC > > Possible interrupt unsafe locking scenario: > > CPU0 CPU1 > ---- ---- > lock(lockC); > local_irq_disable(); > lock(&rq->lock); > lock(lockA); > > lock(&rq->lock) > > *** DEADLOCK *** Cool stuff. I always have to twist my brain around those splats as well :) Thanks, tglx