From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: eric.dumazet@gmail.com
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org
Subject: Fw: rcu warning
Date: Wed, 22 Sep 2010 14:44:38 -0700 [thread overview]
Message-ID: <20100922214438.GN2435@linux.vnet.ibm.com> (raw)
> Date: Wed, 22 Sep 2010 13:52:28 -0700
> From: Andrew Morton <akpm@linux-foundation.org>
> To: "Paul E. McKenney" <paulmck@us.ibm.com>
> Subject: rcu warning
> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; x86_64-pc-linux-gnu)
>
> [ 56.803750]
> [ 56.803752] ===================================================
> [ 56.804082] [ INFO: suspicious rcu_dereference_check() usage. ]
> [ 56.804249] ---------------------------------------------------
> [ 56.804421] include/linux/inetdevice.h:219 invoked rcu_dereference_check() without protection!
> [ 56.804708]
> [ 56.804709] other info that might help us debug this:
> [ 56.804710]
> [ 56.805183]
> [ 56.805184] rcu_scheduler_active = 1, debug_locks = 1
> [ 56.805501] 3 locks held by kworker/0:1/0:
> [ 56.805664] #0: (&in_dev->mr_ifc_timer){+.-...}, at: [<ffffffff81042466>] run_timer_softirq+0xfd/0x226
> [ 56.806126] #1: (&in_dev->mc_list_lock){++.-..}, at: [<ffffffff8133e81d>] igmp_ifc_timer_expire+0x2a/0x221
> [ 56.806588] #2: (&(&im->lock)->rlock){+.-...}, at: [<ffffffff8133e948>] igmp_ifc_timer_expire+0x155/0x221
> [ 56.807043]
> [ 56.807044] stack backtrace:
> [ 56.807364] Pid: 0, comm: kworker/0:1 Not tainted 2.6.36-rc5-mm1 #1
> [ 56.807561] Call Trace:
> [ 56.807723] <IRQ> [<ffffffff8105b88b>] lockdep_rcu_dereference+0x99/0xa2
> [ 56.807948] [<ffffffff8130dc66>] __ip_route_output_key+0x34f/0xb19
> [ 56.808120] [<ffffffff8130d94a>] ? __ip_route_output_key+0x33/0xb19
> [ 56.814367] [<ffffffff8130e453>] ip_route_output_flow+0x23/0x1ee
> [ 56.814536] [<ffffffff8130e62c>] ip_route_output_key+0xe/0x10
> [ 56.814704] [<ffffffff8133e19d>] igmpv3_newpack+0x7f/0x1c2
> [ 56.814873] [<ffffffff8133e30d>] add_grhead+0x2d/0x94
> [ 56.815039] [<ffffffff8133e6c2>] add_grec+0x34e/0x38c
> [ 56.815206] [<ffffffff8133e9a8>] igmp_ifc_timer_expire+0x1b5/0x221
> [ 56.815375] [<ffffffff810424e8>] run_timer_softirq+0x17f/0x226
> [ 56.815547] [<ffffffff81042466>] ? run_timer_softirq+0xfd/0x226
> [ 56.815715] [<ffffffff8133e7f3>] ? igmp_ifc_timer_expire+0x0/0x221
> [ 56.815885] [<ffffffff8103ca8f>] __do_softirq+0xa5/0x13a
> [ 56.816051] [<ffffffff8100390c>] call_softirq+0x1c/0x28
> [ 56.816219] [<ffffffff81004eba>] do_softirq+0x38/0x82
> [ 56.816385] [<ffffffff8103c9e8>] irq_exit+0x47/0x49
> [ 56.816553] [<ffffffff81019ce3>] smp_apic_timer_interrupt+0x88/0x96
> [ 56.816722] [<ffffffff810033d3>] apic_timer_interrupt+0x13/0x20
> [ 56.816888] <EOI> [<ffffffff8138607a>] ? __atomic_notifier_call_chain+0x0/0x84
> [ 56.817215] [<ffffffff81009a9b>] ? mwait_idle+0x65/0x71
> [ 56.817382] [<ffffffff81009a91>] ? mwait_idle+0x5b/0x71
> [ 56.817549] [<ffffffff810014ca>] cpu_idle+0x48/0x66
> [ 56.817716] [<ffffffff8137b4da>] start_secondary+0x1b9/0x1bd
> [ 56.817883] [<ffffffff8137b321>] ? start_secondary+0x0/0x1bd
Hello, Eric,
In linux/master, there is an rcu_read_lock_bh() in the call path, but
an rcu_dereference() instead of an rcu_dereference_bh(). Thoughts?
(I have asked Andrew what kernel this is against -- I don't see the
rcu_read_lock() that I would expect to see in the lockdep output.)
Thanx, Paul
> We seem to be getting way too many of these.
>
> ----- End forwarded message -----
next reply other threads:[~2010-09-22 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 21:44 Paul E. McKenney [this message]
2010-09-22 21:47 ` Fw: rcu warning Andrew Morton
2010-09-22 23:11 ` Paul E. McKenney
2010-09-22 23:04 ` Eric Dumazet
2010-09-22 23:12 ` Paul E. McKenney
2010-09-24 7:46 ` [PATCH net-next-2.6] net: fix rcu use in ip_route_output_slow Eric Dumazet
2010-09-27 2:05 ` David Miller
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=20100922214438.GN2435@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).