From: Valdis.Kletnieks@vt.edu
To: akpm@linux-foundation.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: mmotm 2010-11-23 - lockdep whinge in e1000e driver
Date: Tue, 23 Nov 2010 23:52:34 -0500 [thread overview]
Message-ID: <5622.1290574354@localhost> (raw)
In-Reply-To: Your message of "Tue, 23 Nov 2010 16:13:06 PST." <201011240045.oAO0jYQ5016010@imap1.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 3240 bytes --]
On Tue, 23 Nov 2010 16:13:06 PST, akpm@linux-foundation.org said:
> The mm-of-the-moment snapshot 2010-11-23-16-12 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
Whinges during boot while bringing up the ethernet interface:
[ 1.081504] ===================================================
[ 1.081507] [ INFO: suspicious rcu_dereference_check() usage. ]
[ 1.081509] ---------------------------------------------------
[ 1.081512] include/linux/inetdevice.h:208 invoked rcu_dereference_check() without protection!
[ 1.081514]
[ 1.081515] other info that might help us debug this:
[ 1.081516]
[ 1.081518]
[ 1.081518] rcu_scheduler_active = 1, debug_locks = 1
[ 1.081521] 3 locks held by swapper/1:
[ 1.081523] #0: (&__lockdep_no_validate__){+.+.+.}, at: [<ffffffff812d0b57>] device_lock+0xf/0x11
[ 1.081534] #1: (&__lockdep_no_validate__){+.+.+.}, at: [<ffffffff812d0b57>] device_lock+0xf/0x11
[ 1.081541] #2: (rtnl_mutex){+.+.+.}, at: [<ffffffff8142dee8>] rtnl_lock+0x12/0x14
[ 1.081549]
[ 1.081550] stack backtrace:
[ 1.081553] Pid: 1, comm: swapper Not tainted 2.6.37-rc3-mmotm1123 #3
[ 1.081555] Call Trace:
[ 1.081562] [<ffffffff81069580>] lockdep_rcu_dereference+0x9d/0xa5
[ 1.081567] [<ffffffff8147b235>] __in_dev_get_rcu.clone.12+0x3f/0x47
[ 1.081571] [<ffffffff8147b24d>] inet_get_link_af_size+0x10/0x1f
[ 1.081575] [<ffffffff8142ce16>] if_nlmsg_size+0xd5/0x111
[ 1.081579] [<ffffffff8142ecf6>] rtmsg_ifinfo+0x1f/0xeb
[ 1.081584] [<ffffffff8105d78e>] ? raw_notifier_call_chain+0xf/0x11
[ 1.081589] [<ffffffff81421ee7>] register_netdevice+0x3ea/0x410
[ 1.081593] [<ffffffff81421f47>] register_netdev+0x3a/0x4c
[ 1.081599] [<ffffffff81551cc2>] e1000_probe+0x986/0xb6f
[ 1.081604] [<ffffffff81237b2e>] local_pci_probe+0x3f/0x70
[ 1.081608] [<ffffffff81237eae>] pci_device_probe+0x65/0x96
[ 1.081614] [<ffffffff8115a82a>] ? sysfs_create_link+0xe/0x10
[ 1.081617] [<ffffffff812d0fe0>] driver_probe_device+0xe8/0x182
[ 1.081621] [<ffffffff812d10c4>] __driver_attach+0x4a/0x6b
[ 1.081625] [<ffffffff812d107a>] ? __driver_attach+0x0/0x6b
[ 1.081629] [<ffffffff812d01cf>] bus_for_each_dev+0x57/0x83
[ 1.081633] [<ffffffff812d0ca5>] driver_attach+0x19/0x1b
[ 1.081637] [<ffffffff812d08e7>] bus_add_driver+0xae/0x205
[ 1.081641] [<ffffffff812d1324>] driver_register+0xb5/0x122
[ 1.081646] [<ffffffff81b455cb>] ? e1000_init_module+0x0/0x3e
[ 1.081650] [<ffffffff812380e4>] __pci_register_driver+0x61/0xcd
[ 1.081654] [<ffffffff81b455cb>] ? e1000_init_module+0x0/0x3e
[ 1.081658] [<ffffffff81b45607>] e1000_init_module+0x3c/0x3e
[ 1.081663] [<ffffffff810002ff>] do_one_initcall+0x7a/0x12f
[ 1.081668] [<ffffffff81b1fd08>] kernel_init+0x15d/0x1e7
[ 1.081672] [<ffffffff810035d4>] kernel_thread_helper+0x4/0x10
[ 1.081678] [<ffffffff8102f845>] ? finish_task_switch+0x3f/0xe3
[ 1.081682] [<ffffffff8155b5c0>] ? restore_args+0x0/0x30
[ 1.081686] [<ffffffff81b1fbab>] ? kernel_init+0x0/0x1e7
[ 1.081690] [<ffffffff810035d0>] ? kernel_thread_helper+0x0/0x10
[ 1.081731] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:24:e8:c6:ad:17
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-11-24 4:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 0:13 mmotm 2010-11-23-16-12 uploaded akpm
2010-11-24 0:13 ` akpm
2010-11-24 4:52 ` Valdis.Kletnieks [this message]
2010-11-24 4:55 ` mmotm 2010-11-23 - WARNING: at drivers/tty/tty_io.c:1331 Valdis.Kletnieks
2010-11-25 15:14 ` Kyle McMartin
2010-11-25 16:44 ` Jiri Slaby
2010-11-25 16:51 ` Jiri Slaby
2010-11-25 17:16 ` [PATCH 1/1] TTY: don't allow reopen when ldisc is changing Jiri Slaby
2010-11-25 17:59 ` Kyle McMartin
2010-11-26 0:28 ` Kyle McMartin
2010-11-26 7:46 ` Jiri Slaby
2010-11-26 13:27 ` Kyle McMartin
2010-11-27 2:59 ` Kyle McMartin
2010-11-27 8:50 ` Jiri Slaby
2010-11-27 9:43 ` Jiri Slaby
2010-11-27 15:11 ` Jiri Slaby
2010-11-27 23:53 ` Kyle McMartin
2010-11-24 5:01 ` mmotm 2010-11-23 + autogroups -> inconsistent lock state Valdis.Kletnieks
2010-11-24 20:25 ` Mike Galbraith
2010-11-24 20:39 ` Mike Galbraith
2010-11-25 6:09 ` Valdis.Kletnieks
2010-12-02 18:16 ` Paul E. McKenney
2010-12-03 3:58 ` Mike Galbraith
2010-11-24 13:56 ` mmotm 2010-11-23-16-12 uploaded Zimny Lech
2010-11-24 13:56 ` Zimny Lech
2010-11-24 18:51 ` mmotm 2010-11-23-16-12 uploaded (olpc) Randy Dunlap
2010-11-24 18:51 ` Randy Dunlap
2010-11-24 19:13 ` Andres Salomon
2010-11-24 19:13 ` Andres Salomon
2010-11-26 16:46 ` Daniel Drake
2010-11-26 16:46 ` Daniel Drake
2010-11-24 19:41 ` [PATCH -mmotm/-next] media: fix timblogiw kconfig & build error Randy Dunlap
2010-11-24 19:41 ` Randy Dunlap
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=5622.1290574354@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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.