linux-kernel - nfsd lockdep snafu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20060725211908.GA3694@redhat.com>
Date:	Tue, 25 Jul 2006 17:19:08 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: nfsd lockdep snafu

>From an rc2-git3 based kernel..

		Dave

=============================================
[ INFO: possible recursive locking detected ]
---------------------------------------------
nfsd/1932 is trying to acquire lock:
 (&inode->i_mutex){--..}, at: [<c06075f9>] mutex_lock+0x21/0x24

but task is already holding lock:
 (&inode->i_mutex){--..}, at: [<c06075f9>] mutex_lock+0x21/0x24

other info that might help us debug this:
2 locks held by nfsd/1932:
 #0:  (hash_sem){----}, at: [<ccfc44e2>] exp_readlock+0xd/0xf [nfsd]
 #1:  (&inode->i_mutex){--..}, at: [<c06075f9>] mutex_lock+0x21/0x24

stack backtrace:
 [<c04051ea>] show_trace_log_lvl+0x54/0xfd
 [<c04057a6>] show_trace+0xd/0x10
 [<c04058bf>] dump_stack+0x19/0x1b
 [<c043b7ae>] __lock_acquire+0x773/0x997
 [<c043bf43>] lock_acquire+0x4b/0x6c
 [<c060748a>] __mutex_lock_slowpath+0xbc/0x20a
 [<c06075f9>] mutex_lock+0x21/0x24
 [<ccfc1d57>] nfsd_setattr+0x2fb/0x4aa [nfsd]
 [<ccfc31e3>] nfsd_create_v3+0x31c/0x48c [nfsd]
 [<ccfc7e12>] nfsd3_proc_create+0x125/0x135 [nfsd]
 [<ccfbe0d4>] nfsd_dispatch+0xc0/0x178 [nfsd]
 [<ccf077c3>] svc_process+0x3a4/0x5ee [sunrpc]
 [<ccfbe5f6>] nfsd+0x197/0x2e1 [nfsd]
 [<c0402005>] kernel_thread_helper+0x5/0xb


-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/