From: Dave Young <hidave.darkstar@gmail.com>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2009-08-04-14-22 uploaded
Date: Wed, 5 Aug 2009 14:39:46 +0800 [thread overview]
Message-ID: <20090805063946.GA1934@darkstar> (raw)
In-Reply-To: <200908042125.n74LP9qY018119@imap1.linux-foundation.org>
Hi andrew,
I see following lockdep warning with this release:
[ 0.474144] INFO: trying to register non-static key.
[ 0.474144] the code is fine but needs lockdep annotation.
[ 0.474144] turning off the locking correctness validator.
[ 0.474144] Pid: 1, comm: swapper Not tainted 2.6.31-rc5-mm1 #7
[ 0.474144] Call Trace:
[ 0.474144] [<c1047f1e>] register_lock_class+0x58/0x241
[ 0.474144] [<c1049ab1>] __lock_acquire+0xac/0xb73
[ 0.474144] [<c1076eb5>] ? __alloc_pages_nodemask+0xe2/0x483
[ 0.474144] [<c1048b64>] ? mark_lock+0x1e/0x1c7
[ 0.474144] [<c1048b64>] ? mark_lock+0x1e/0x1c7
[ 0.474144] [<c1048d50>] ? mark_held_locks+0x43/0x5b
[ 0.474144] [<c10940a6>] ? kmem_cache_alloc+0xac/0x11b
[ 0.474144] [<c104a615>] lock_acquire+0x9d/0xc0
[ 0.474144] [<c12b8b96>] ? netif_addr_lock_bh+0xd/0xf
[ 0.474144] [<c1330feb>] _spin_lock_bh+0x20/0x2f
[ 0.474144] [<c12b8b96>] ? netif_addr_lock_bh+0xd/0xf
[ 0.474144] [<c12b8b96>] netif_addr_lock_bh+0xd/0xf
[ 0.474144] [<c12bc3c3>] alloc_netdev_mq+0xf9/0x1a5
[ 0.474144] [<c121f016>] ? loopback_setup+0x0/0x74
[ 0.474144] [<c1578d49>] loopback_net_init+0x20/0x5d
[ 0.474144] [<c12b7907>] register_pernet_operations+0x13/0x15
[ 0.474144] [<c12b7970>] register_pernet_device+0x1f/0x47
[ 0.474144] [<c157ee8d>] net_dev_init+0xfe/0x14d
[ 0.474144] [<c1001137>] do_one_initcall+0x4a/0x11a
[ 0.474144] [<c157ed8f>] ? net_dev_init+0x0/0x14d
[ 0.474144] [<c1067e00>] ? register_irq_proc+0x64/0xa8
[ 0.474144] [<c1067e97>] ? init_irq_proc+0x53/0x60
[ 0.474144] [<c1557535>] kernel_init+0x129/0x17a
[ 0.474144] [<c155740c>] ? kernel_init+0x0/0x17a
[ 0.474144] [<c1003d47>] kernel_thread_helper+0x7/0x10
--
Regards
dave
next prev parent reply other threads:[~2009-08-05 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 21:25 mmotm 2009-08-04-14-22 uploaded akpm
2009-08-04 22:50 ` mmotm 2009-08-04-14-22 uploaded (ummunotify) Randy Dunlap
2009-08-04 23:16 ` Andrew Morton
2009-08-05 0:38 ` Roland Dreier
2009-08-05 4:47 ` Roland Dreier
2009-08-05 15:19 ` Randy Dunlap
2009-08-05 1:48 ` [PATCH -mmotm] staging/udlfb: fix printk format warning Randy Dunlap
2009-08-05 1:54 ` [PATCH -mmotm] xfrm4: fix build when SYSCTLs are disabled Randy Dunlap
2009-08-05 3:20 ` David Miller
2009-08-05 6:39 ` Dave Young [this message]
2009-08-05 7:06 ` mmotm 2009-08-04-14-22 uploaded Andrew Morton
2009-08-05 7:14 ` Eric Dumazet
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=20090805063946.GA1934@darkstar \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.