From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753026Ab1KBWK3 (ORCPT ); Wed, 2 Nov 2011 18:10:29 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:55470 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751870Ab1KBWK1 (ORCPT ); Wed, 2 Nov 2011 18:10:27 -0400 X-Authority-Analysis: v=1.1 cv=PzmnriOiyqYdyw8suerSEFMr8oy2Ua58JL+Rk7iuDKE= c=1 sm=0 a=wom5GMh1gUkA:10 a=5SG0PmZfjMsA:10 a=kj9zAlcOel0A:10 a=ZycB6UtQUfgMyuk2+PxD7w==:17 a=HrKklt6QmJN0OufAPDIA:9 a=CjuIK1q_8ugA:10 a=ZycB6UtQUfgMyuk2+PxD7w==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.80.29 Date: Wed, 2 Nov 2011 18:10:23 -0400 From: Steven Rostedt To: Simon Kirby Cc: Thomas Gleixner , David Miller , Peter Zijlstra , Linus Torvalds , Linux Kernel Mailing List , Dave Jones , Martin Schwidefsky , Ingo Molnar , Network Development Subject: Re: Linux 3.1-rc9 Message-ID: <20111102221023.GA27457@home.goodmis.org> References: <1318879396.4172.92.camel@twins> <1318928713.21167.4.camel@twins> <20111018182046.GF1309@hostway.ca> <20111024190203.GA24410@hostway.ca> <20111025202049.GB25043@hostway.ca> <20111031173246.GA10614@hostway.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111031173246.GA10614@hostway.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thomas pointed me here. On Mon, Oct 31, 2011 at 10:32:46AM -0700, Simon Kirby wrote: > [104661.244767] > [104661.244767] Possible unsafe locking scenario: > [104661.244767] > [104661.244767] CPU0 CPU1 > [104661.244767] ---- ---- > [104661.244767] lock(slock-AF_INET); > [104661.244767] lock(slock-AF_INET); > [104661.244767] lock(slock-AF_INET); > [104661.244767] lock(slock-AF_INET); > [104661.244767] > [104661.244767] *** DEADLOCK *** > [104661.244767] Bah, I used the __print_lock_name() function to show the lock names in the above, which leaves off the subclass number. I'll go write up a patch that fixes that. Thanks, -- Steve