From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: netdev@vger.kernel.org
Subject: Re: linux/netpoll.h:67 invoked rcu_dereference warning at boot
Date: Wed, 22 Sep 2010 15:30:06 +0200 [thread overview]
Message-ID: <1285162206.2639.420.camel@edumazet-laptop> (raw)
In-Reply-To: <20100922132014.GA8853@basil.fritz.box>
Le mercredi 22 septembre 2010 à 15:20 +0200, Andi Kleen a écrit :
> When booting a recent Linus tree with debugging enabled I get
> the following warning at boot.
>
> I haven't looked into it closely.
>
> -Andi
>
> ===================================================
> [ INFO: suspicious rcu_dereference_check() usage. ]
> ---------------------------------------------------
> /home/lsrc/git/linux-work2/include/linux/netpoll.h:67 invoked rcu_dereferenceeck() without protection!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 1, debug_locks = 1
> 1 lock held by iceccd/2574:
> #0: (sk_lock-AF_INET){+.+.+.}, at: [<ffffffff81721bf9>] udp_sendmsg+0x289/00
>
> stack backtrace:
> Pid: 2574, comm: iceccd Not tainted 2.6.36-rc4-00228-g5647824 #1
> Call Trace:
> [<ffffffff81090a24>] lockdep_rcu_dereference+0xa4/0xc0
> [<ffffffff816d3475>] netif_rx+0x215/0x240
> [<ffffffff81135fbf>] ? cache_alloc_debugcheck_after+0x5f/0x280
> [<ffffffff8104cc61>] ? get_parent_ip+0x11/0x50
> [<ffffffff816d36b3>] netif_rx_ni+0x23/0x80
> [<ffffffff816fd3f3>] ip_dev_loopback_xmit+0x83/0xf0
> [<ffffffff816fddfa>] ip_mc_output+0x18a/0x220
> [<ffffffff816fd53d>] ip_local_out+0x2d/0x80
> [<ffffffff816ff414>] ip_push_pending_frames+0x284/0x420
> [<ffffffff81720586>] udp_push_pending_frames+0x146/0x3e0
> [<ffffffff81721bf9>] ? udp_sendmsg+0x289/0x720
> [<ffffffff81721de4>] udp_sendmsg+0x474/0x720
> [<ffffffff8105ec82>] ? local_bh_enable_ip+0x82/0x100
> [<ffffffff8172aee4>] inet_sendmsg+0xc4/0x160
> [<ffffffff8172ae20>] ? inet_sendmsg+0x0/0x160
> [<ffffffff816bddd0>] sock_sendmsg+0xc0/0xf0
> [<ffffffff8110e03a>] ? might_fault+0x7a/0xd0
> [<ffffffff8110e03a>] ? might_fault+0x7a/0xd0
> [<ffffffff8110e083>] ? might_fault+0xc3/0xd0
> [<ffffffff8110e03a>] ? might_fault+0x7a/0xd0
> [<ffffffff816bfe80>] ? move_addr_to_kernel+0x50/0x60
> [<ffffffff816c0ba5>] sys_sendto+0xf5/0x130
> [<ffffffff8100311b>] system_call_fastpath+0x16/0x1b
>
>
Thanks Andi
I believe I sent a patch this morning
http://lkml.org/lkml/2010/9/22/35
prev parent reply other threads:[~2010-09-22 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 13:20 linux/netpoll.h:67 invoked rcu_dereference warning at boot Andi Kleen
2010-09-22 13:30 ` Eric Dumazet [this message]
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=1285162206.2639.420.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=andi@firstfloor.org \
--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