From: Andrew Morton <akpm@linux-foundation.org>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@tv-sign.ru>,
Neil Brown <neilb@suse.de>
Subject: Re: [2.6.20] BUG: workqueue leaked lock
Date: Thu, 15 Mar 2007 11:06:28 -0800 [thread overview]
Message-ID: <20070315110628.8bd2c07b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070313165014.GE31960@vanheusden.com>
> On Tue, 13 Mar 2007 17:50:14 +0100 Folkert van Heusden <folkert@vanheusden.com> wrote:
> ...
> [ 1756.728209] BUG: workqueue leaked lock or atomic: nfsd4/0x00000000/3577
> [ 1756.728271] last function: laundromat_main+0x0/0x69 [nfsd]
> [ 1756.728392] 2 locks held by nfsd4/3577:
> [ 1756.728435] #0: (client_mutex){--..}, at: [<c1205b88>] mutex_lock+0x8/0xa
> [ 1756.728679] #1: (&inode->i_mutex){--..}, at: [<c1205b88>] mutex_lock+0x8/0xa
> [ 1756.728923] [<c1003d57>] show_trace_log_lvl+0x1a/0x30
> [ 1756.729015] [<c1003d7f>] show_trace+0x12/0x14
> [ 1756.729103] [<c1003e79>] dump_stack+0x16/0x18
> [ 1756.729187] [<c102c2e8>] run_workqueue+0x167/0x170
> [ 1756.729276] [<c102c437>] worker_thread+0x146/0x165
> [ 1756.729368] [<c102f797>] kthread+0x97/0xc4
> [ 1756.729456] [<c1003bdb>] kernel_thread_helper+0x7/0x10
> [ 1756.729547] =======================
> [ 1792.436492] svc: unknown version (0 for prog 100003, nfsd)
> [ 1846.683648] BUG: workqueue leaked lock or atomic: nfsd4/0x00000000/3577
> [ 1846.683701] last function: laundromat_main+0x0/0x69 [nfsd]
> [ 1846.683832] 2 locks held by nfsd4/3577:
> [ 1846.683885] #0: (client_mutex){--..}, at: [<c1205b88>] mutex_lock+0x8/0xa
> [ 1846.683980] #1: (&inode->i_mutex){--..}, at: [<c1205b88>] mutex_lock+0x8/0xa
> [ 1846.683988] [<c1003d57>] show_trace_log_lvl+0x1a/0x30
> [ 1846.683994] [<c1003d7f>] show_trace+0x12/0x14
> [ 1846.683997] [<c1003e79>] dump_stack+0x16/0x18
> [ 1846.684001] [<c102c2e8>] run_workqueue+0x167/0x170
> [ 1846.684006] [<c102c437>] worker_thread+0x146/0x165
> [ 1846.684012] [<c102f797>] kthread+0x97/0xc4
> [ 1846.684023] [<c1003bdb>] kernel_thread_helper+0x7/0x10
Oleg, that's a fairly incomprehensible message we have in there. Can you
please explain what it means?
next prev parent reply other threads:[~2007-03-15 19:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 16:50 [2.6.20] BUG: workqueue leaked lock Folkert van Heusden
2007-03-15 19:06 ` Andrew Morton [this message]
2007-03-15 19:17 ` Folkert van Heusden
2007-03-16 14:49 ` Jarek Poplawski
2007-03-20 11:17 ` dquot.c: possible circular locking " Jarek Poplawski
2007-03-20 11:22 ` Jarek Poplawski
2007-03-20 11:31 ` Jarek Poplawski
2007-03-20 12:19 ` Jan Kara
2007-03-20 13:35 ` Arjan van de Ven
2007-03-20 14:21 ` Jan Kara
2007-03-20 14:18 ` Arjan van de Ven
2007-03-20 13:44 ` Jarek Poplawski
2007-03-20 14:00 ` Jan Kara
2007-03-16 8:41 ` Peter Zijlstra
2007-03-16 11:39 ` Andrew Morton
2007-03-19 6:24 ` Neil Brown
2007-03-20 9:37 ` [PATCH] " Jarek Poplawski
2007-03-20 16:07 ` Oleg Nesterov
2007-03-21 8:05 ` Jarek Poplawski
2007-03-21 14:46 ` Oleg Nesterov
2007-03-21 15:16 ` Jarek Poplawski
2007-03-21 15:17 ` Folkert van Heusden
2007-03-21 15:29 ` Oleg Nesterov
2007-03-21 18:16 ` Oleg Nesterov
2007-03-22 6:11 ` [PATCH] lockdep: lockdep_depth vs. debug_locks " Jarek Poplawski
2007-03-22 6:28 ` Andrew Morton
2007-03-22 7:06 ` Jarek Poplawski
2007-03-22 7:23 ` Jarek Poplawski
2007-03-22 7:13 ` Jarek Poplawski
2007-03-22 8:26 ` Jarek Poplawski
2007-03-22 6:57 ` [PATCH] lockdep: debug_show_all_locks & debug_show_held_locks vs. debug_locks Jarek Poplawski
2007-03-22 7:23 ` Peter Zijlstra
2007-03-22 9:06 ` Ingo Molnar
2007-03-22 7:22 ` [PATCH] lockdep: lockdep_depth vs. debug_locks Re: [2.6.20] BUG: workqueue leaked lock Peter Zijlstra
2007-03-22 9:06 ` Ingo Molnar
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=20070315110628.8bd2c07b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=oleg@tv-sign.ru \
/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;
as well as URLs for NNTP newsgroup(s).