From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: nfsd lockdep snafu
Date: Tue, 25 Jul 2006 17:19:08 -0400 [thread overview]
Message-ID: <20060725211908.GA3694@redhat.com> (raw)
>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
reply other threads:[~2006-07-25 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060725211908.GA3694@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox