Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932099AbWICU0i (ORCPT ); Sun, 3 Sep 2006 16:26:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932101AbWICU0i (ORCPT ); Sun, 3 Sep 2006 16:26:38 -0400 Received: from khc.piap.pl ([195.187.100.11]:56487 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S932099AbWICU0h (ORCPT ); Sun, 3 Sep 2006 16:26:37 -0400 To: Subject: 2.6.18rc5: NFSd possible recursive locking From: Krzysztof Halasa Date: Sun, 03 Sep 2006 22:26:35 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1365 Lines: 41 Hi, another one (details available on request): [ INFO: possible recursive locking detected ] --------------------------------------------- nfsd/1566 is trying to acquire lock: (&inode->i_mutex){--..}, at: [] mutex_lock+0x1c/0x20 but task is already holding lock: (&inode->i_mutex){--..}, at: [] mutex_lock+0x1c/0x20 other info that might help us debug this: 2 locks held by nfsd/1566: #0: (hash_sem){..--}, at: [] exp_readlock+0xd/0x10 #1: (&inode->i_mutex){--..}, at: [] mutex_lock+0x1c/0x20 stack backtrace: [] show_trace+0x12/0x20 [] dump_stack+0x19/0x20 [] __lock_acquire+0x8db/0xd70 [] lock_acquire+0x76/0xa0 [] __mutex_lock_slowpath+0x66/0x250 [] mutex_lock+0x1c/0x20 [] nfsd_setattr+0x46d/0x5b0 [] nfsd_create_v3+0x4da/0x540 [] nfsd3_proc_create+0x104/0x170 [] nfsd_dispatch+0x88/0x1e0 [] svc_process+0x3f4/0x6e0 [] nfsd+0x191/0x300 [] kernel_thread_helper+0x5/0x10 -- Krzysztof Halasa -- VGER BF report: U 0.502044 - 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/