From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc6-mm1
Date: Thu, 8 Jun 2006 01:00:47 -0400 [thread overview]
Message-ID: <20060608050047.GB16729@redhat.com> (raw)
In-Reply-To: <20060607104724.c5d3d730.akpm@osdl.org>
On Wed, Jun 07, 2006 at 10:47:24AM -0700, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc6/2.6.17-rc6-mm1/
>
> - Many more lockdep updates
Needs more.
====================================
[ BUG: possible deadlock detected! ]
------------------------------------
nfsd/11429 is trying to acquire lock:
(&inode->i_mutex){--..}, at: [<c032286a>] mutex_lock+0x21/0x24
but task is already holding lock:
(&inode->i_mutex){--..}, at: [<c032286a>] mutex_lock+0x21/0x24
which could potentially lead to deadlocks!
other info that might help us debug this:
2 locks held by nfsd/11429:
#0: (hash_sem){----}, at: [<d10d0364>] exp_readlock+0x0/0x3e [nfsd]
#1: (&inode->i_mutex){--..}, at: [<c032286a>] mutex_lock+0x21/0x24
stack backtrace:
[<c0104966>] show_trace_log_lvl+0x54/0xfd
[<c0104f1a>] show_trace+0xd/0x10
[<c010502f>] dump_stack+0x19/0x1b
[<c013b2d4>] __lockdep_acquire+0x8f6/0x912
[<c013b346>] lockdep_acquire+0x56/0x6f
[<c03226cf>] __mutex_lock_slowpath+0xae/0x228
[<c032286a>] mutex_lock+0x21/0x24
[<d10cdb64>] nfsd_setattr+0x2d3/0x49f [nfsd]
[<d10ceecd>] nfsd_create_v3+0x319/0x4aa [nfsd]
[<d10d413e>] nfsd3_proc_create+0x125/0x135 [nfsd]
[<d10ca0d4>] nfsd_dispatch+0xc0/0x178 [nfsd]
[<d0ee89e9>] svc_process+0x38d/0x5d5 [sunrpc]
[<d10ca581>] nfsd+0x18b/0x302 [nfsd]
[<c0102005>] kernel_thread_helper+0x5/0xb
It's too close to bedtime for me, and on a cursory examination,
I don't even see where nfsd_setattr touches a mutex.
This was triggered by a simple 'touch foo' over an nfs v3 mount.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-06-08 5:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 21:23 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:07 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 22:36 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 23:54 ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08 0:31 ` 2.6.17-rc6-mm1 Chris Wright
2006-06-08 6:30 ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08 7:26 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 21:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:11 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-08 3:19 ` 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 15:13 ` lockdep wierdness - was 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 10:06 ` NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1) Duncan Sands
2006-06-12 14:35 ` Ingo Molnar
2006-06-08 12:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:31 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:40 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 23:23 ` [PATCH] ignore smp_locks section warnings from init/exit code Randy.Dunlap
2006-06-08 0:04 ` Randy.Dunlap
2006-06-08 2:11 ` Jeff Dike
2006-06-08 2:32 ` Randy.Dunlap
2006-06-08 4:21 ` Jeff Dike
2006-06-08 4:29 ` Randy.Dunlap
2006-06-08 15:44 ` Randy.Dunlap
2006-06-08 18:35 ` Sam Ravnborg
2006-06-11 23:25 ` Jeff Dike
2006-06-12 0:17 ` Randy.Dunlap
2006-06-12 2:29 ` Jeff Dike
2006-06-12 2:52 ` Randy.Dunlap
2006-06-08 2:25 ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08 2:46 ` 2.6.17-rc6-mm1 Randy.Dunlap
2006-06-08 5:43 ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08 6:46 ` 2.6.17-rc6-mm1 Gerd Hoffmann
2006-06-07 23:14 ` 2.6.17-rc6-mm1 Martin Bligh
2006-06-07 23:55 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-08 1:09 ` 2.6.17-rc6-mm1 Grant Coady
2006-06-08 5:00 ` Dave Jones [this message]
2006-06-20 17:42 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-20 20:24 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-20 20:38 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 6:23 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-21 8:15 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 18:42 ` 2.6.17-rc6-mm1 Dave Jones
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=20060608050047.GB16729@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--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