LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Hansen <haveblue@us.ibm.com>,
penguin-kernel@i-love.sakura.ne.jp, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Greg KH <greg@kroah.com>,
Kay Sievers <kay.sievers@vrfy.org>, Ingo Molnar <mingo@elte.hu>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [2.6.25-rc5-mm1] BUG() at mnt_want_write().
Date: Wed, 12 Mar 2008 10:25:18 +0100 [thread overview]
Message-ID: <1205313918.8514.215.camel@twins> (raw)
In-Reply-To: <20080311202212.9fe1e5c1.akpm@linux-foundation.org>
On Tue, 2008-03-11 at 20:22 -0700, Andrew Morton wrote:
> On Tue, 11 Mar 2008 20:03:30 -0700 Dave Hansen <haveblue@us.ibm.com> wrote:
>
> > On Wed, 2008-03-12 at 10:37 +0900, penguin-kernel@i-love.sakura.ne.jp
> > ...
> > > checking TSC synchronization [CPU#0 -> CPU#1]: passed.
> > > Brought up 2 CPUs
> > > khelper used greatest stack depth: 2684 bytes left
> > > net_namespace: 320 bytes
> > > NET: Registered protocol family 16
> > > INFO: trying to register non-static key.
It means the lock_class_key ended up in non-static storage.
In practise it often means you initialized a on-stack structure
incorrectly. DECLARE_WAIT_QUEUE_HEAD() vs
DECLARE_WAIT_QUEUE_HEAD_ONSTACK() for example.
> > > the code is fine but needs lockdep annotation.
> > > turning off the locking correctness validator.
> > > Pid: 1, comm: swapper Not tainted 2.6.25-rc5-mm1 #1
> > > [<c013dd91>] __lock_acquire+0x194/0x6a3
> > > [<c0167ded>] ? cache_free_debugcheck+0x1fd/0x219
> > > [<c0168938>] ? kfree+0xdb/0xe5
> > > [<c013e775>] lock_acquire+0x6a/0x87
> > > [<c01368e4>] ? down+0xc/0x2f
> > > [<c03492b1>] _spin_lock_irqsave+0x25/0x55
> > > [<c01368e4>] ? down+0xc/0x2f
> > > [<c01368e4>] down+0xc/0x2f
> > > [<c022caf3>] device_add+0x152/0x243
> > > [<c022cbf6>] device_register+0x12/0x15
> > > [<c022ce9b>] device_create+0x76/0x90
> > > [<c04a1861>] vtconsole_class_init+0x72/0xb9
> > > [<c048d8ae>] ? kernel_init+0x0/0x88
> > > [<c048d784>] do_initcalls+0x59/0x134
> > > [<c014bcb1>] ? register_irq_proc+0xb1/0xca
> > > [<c01a0000>] ? proc_symlink+0x5/0x73
> > > [<c048d8ae>] ? kernel_init+0x0/0x88
> > > [<c048d87b>] do_basic_setup+0x1c/0x1e
> > > [<c048d8fb>] kernel_init+0x4d/0x88
> > > [<c01045b7>] kernel_thread_helper+0x7/0x10
> > > =======================
> >
/me & git fetch mm && git checkout mm/v2.6.25-rc5-mm1
/me twiddles thumbs..
/me tries to untangle the sysfs stuff, finds nothing wrong, looks at
semaphore code, and.. the winner is: Matthew messed up the semaphores.
Tssk, rewriting locking primitives and not using lockdep...
Compile tested defconfig with lockdep and !lockdep.
---
Subject: lockdep: fixup the new semaphore implementation
The new semaphores failed to properly initialize its spinlock. Non
static spinlocks should use spin_lock_init(). Alternatively you should
supply a static key yourself.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
include/linux/semaphore.h | 4 ++++
1 file changed, 4 insertions(+)
Index: linux-2.6/include/linux/semaphore.h
===================================================================
--- linux-2.6.orig/include/linux/semaphore.h
+++ linux-2.6/include/linux/semaphore.h
@@ -41,7 +41,11 @@ struct semaphore {
static inline void sema_init(struct semaphore *sem, int val)
{
+ static struct lock_class_key __key;
+
*sem = (struct semaphore) __SEMAPHORE_INITIALIZER(*sem, val);
+
+ lockdep_init_map(&sem->lock.dep_map, "semaphore->lock", &__key, 0);
}
#define init_MUTEX(sem) sema_init(sem, 1)
next prev parent reply other threads:[~2008-03-12 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 1:37 penguin-kernel
2008-03-12 3:03 ` Dave Hansen
2008-03-12 3:22 ` Andrew Morton
2008-03-12 9:25 ` Peter Zijlstra [this message]
2008-03-12 16:52 ` Matthew Wilcox
2008-03-13 0:21 ` Tetsuo Handa
2008-03-13 20:41 ` fix for boot-time mnt_want_write() bug Dave Hansen
2008-03-14 0:15 ` Tetsuo Handa
2008-03-12 5:46 ` [2.6.25-rc5-mm1] BUG() at mnt_want_write() Tetsuo Handa
2008-03-12 6:35 ` Tetsuo Handa
2008-03-12 3:43 ` Dave Hansen
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=1205313918.8514.215.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=haveblue@us.ibm.com \
--cc=hch@lst.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--subject='Re: [2.6.25-rc5-mm1] BUG() at mnt_want_write().' \
/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
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).