From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18rc5: NFSd possible recursive locking
Date: Tue, 05 Sep 2006 08:12:13 +0200 [thread overview]
Message-ID: <1157436733.14324.9.camel@twins> (raw)
In-Reply-To: <m3slj8ae84.fsf@defiant.localdomain>
On Sun, 2006-09-03 at 22:26 +0200, Krzysztof Halasa wrote:
> Hi,
>
> another one (details available on request):
>
> [ INFO: possible recursive locking detected ]
> ---------------------------------------------
> nfsd/1566 is trying to acquire lock:
> (&inode->i_mutex){--..}, at: [<c0334e0c>] mutex_lock+0x1c/0x20
>
> but task is already holding lock:
> (&inode->i_mutex){--..}, at: [<c0334e0c>] mutex_lock+0x1c/0x20
>
> other info that might help us debug this:
> 2 locks held by nfsd/1566:
> #0: (hash_sem){..--}, at: [<c01b292d>] exp_readlock+0xd/0x10
> #1: (&inode->i_mutex){--..}, at: [<c0334e0c>] mutex_lock+0x1c/0x20
>
> stack backtrace:
> [<c0103522>] show_trace+0x12/0x20
> [<c0103b79>] dump_stack+0x19/0x20
> [<c012dfab>] __lock_acquire+0x8db/0xd70
> [<c012e7b6>] lock_acquire+0x76/0xa0
> [<c0334c06>] __mutex_lock_slowpath+0x66/0x250
> [<c0334e0c>] mutex_lock+0x1c/0x20
> [<c01afd1d>] nfsd_setattr+0x46d/0x5b0
> [<c01b12da>] nfsd_create_v3+0x4da/0x540
> [<c01b6574>] nfsd3_proc_create+0x104/0x170
> [<c01ab7d8>] nfsd_dispatch+0x88/0x1e0
> [<c03248d4>] svc_process+0x3f4/0x6e0
> [<c01abce1>] nfsd+0x191/0x300
> [<c0100c85>] kernel_thread_helper+0x5/0x10
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/broken-out/nfsd-lockdep-annotation.patch
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/broken-out/knfsd-nfsd-lockdep-annotation-fix.patch
Do those patches fix it?
next prev parent reply other threads:[~2006-09-05 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 20:26 2.6.18rc5: NFSd possible recursive locking Krzysztof Halasa
2006-09-04 14:03 ` Dave Jones
2006-09-05 6:12 ` Peter Zijlstra [this message]
2006-09-05 18:18 ` Krzysztof Halasa
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=1157436733.14324.9.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=khc@pm.waw.pl \
--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