Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755352Ab2FDAQw (ORCPT ); Sun, 3 Jun 2012 20:16:52 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:35904 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755280Ab2FDAQv (ORCPT ); Sun, 3 Jun 2012 20:16:51 -0400 MIME-Version: 1.0 In-Reply-To: <20120604000059.GA14144@redhat.com> References: <20120603223617.GB7707@redhat.com> <20120604000059.GA14144@redhat.com> From: Linus Torvalds Date: Sun, 3 Jun 2012 17:16:30 -0700 X-Google-Sender-Auth: 5rpLQSpnyN9KoQl3zAHZDyiQ41k Message-ID: Subject: Re: processes hung after sys_renameat, and 'missing' processes To: Dave Jones , Al Viro , Linux Kernel , Peter Zijlstra Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 865 Lines: 21 On Sun, Jun 3, 2012 at 5:00 PM, Dave Jones wrote: > > sysrq-d: http://fpaste.org/ow9O/ Ugh. I'm adding PeterZ to the cc, just to see if he can make more sense of it. Peter, is there no way to make the lock thing print not just the lock class name, but also the pointer to the actual *instance* of the lock held? Also, it's a bit unclear to me, but I *think* that most of those users don't actually "hold" the lock - they are waiting for it. Yes/no? Does the lockdep information have the capability to distinguish between "waiting for" vs "actually successfully owns the lock"? Linus -- 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/