Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755000Ab2FCXH6 (ORCPT ); Sun, 3 Jun 2012 19:07:58 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:46526 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752130Ab2FCXH5 (ORCPT ); Sun, 3 Jun 2012 19:07:57 -0400 MIME-Version: 1.0 In-Reply-To: <20120603223617.GB7707@redhat.com> References: <20120603223617.GB7707@redhat.com> From: Linus Torvalds Date: Sun, 3 Jun 2012 16:07:35 -0700 X-Google-Sender-Auth: Icpva8dee3DLkuQV9z12-taxYlE Message-ID: Subject: Re: processes hung after sys_renameat, and 'missing' processes To: Dave Jones , Al Viro , Linux Kernel 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: 1188 Lines: 29 On Sun, Jun 3, 2012 at 3:36 PM, Dave Jones wrote: > > It's still up and in this state if you want me to gather any further info > before I reboot it. You seem to have lockdep enabled, since I see the lock information, but presumably you didn't get a lockdep splat before this? Also, sysrq-w is usually way more interesting than 't' when there are processes stuck on a mutex. Because yes, it looks like you have a boattload of trinity processes stuck on an inode mutex. Looks like every single one of them is in 'lock_rename()'. It *shouldn't* be an ABBA deadlock, since lockdep should have noticed that, but who knows. It looks like the lock information is somewhat truncated. I suspect the dmesg buffer had filled up with all the task data. Can you do just "sysrq-d" for the lock information (and maybe separately "sysrq-w" for the blocked tasks)? The non-truncated lock data might tell us more. 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/