From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dimitris Michailidis <dm@chelsio.com>
Cc: netdev@vger.kernel.org
Subject: Re: net-next rcu_dereference_check() warning
Date: Mon, 27 Sep 2010 18:45:12 +0200 [thread overview]
Message-ID: <1285605912.3017.111.camel@edumazet-laptop> (raw)
In-Reply-To: <4CA0C691.1090001@chelsio.com>
Le lundi 27 septembre 2010 à 09:30 -0700, Dimitris Michailidis a écrit :
> With today's net-next I am getting the below. It appears to be recent, it
> wasn't happening with the net-next I was using last week.
>
> ===================================================
> [ INFO: suspicious rcu_dereference_check() usage. ]
> ---------------------------------------------------
> /build/net-next-2.6/include/linux/netpoll.h:67 invoked
> rcu_dereference_check() without protection!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 1, debug_locks = 0
> 1 lock held by ypbind/5046:
> #0: (sk_lock-AF_INET){+.+.+.}, at: [<ffffffff81503139>]
> udp_sendmsg+0x3fd/0x5dc
>
> stack backtrace:
> Pid: 5046, comm: ypbind Not tainted 2.6.36-rc3+ #16
> Call Trace:
> [<ffffffff810668e4>] lockdep_rcu_dereference+0xaa/0xb3
> [<ffffffff814b8d09>] netif_rx+0x53/0x1cf
> [<ffffffff810313b7>] ? get_parent_ip+0x11/0x41
> [<ffffffff814b9068>] netif_rx_ni+0x23/0x5d
> [<ffffffff814e57a9>] ip_dev_loopback_xmit+0xc5/0xcb
> [<ffffffff814e593c>] ip_mc_output+0x18d/0x1a5
> [<ffffffff814e30ec>] ip_local_out+0x62/0x66
> [<ffffffff814e33cb>] ip_push_pending_frames+0x2db/0x337
> [<ffffffff81501b55>] udp_push_pending_frames+0x2de/0x34c
> [<ffffffff81503139>] ? udp_sendmsg+0x3fd/0x5dc
> [<ffffffff8150322a>] udp_sendmsg+0x4ee/0x5dc
> [<ffffffff8150aa74>] inet_sendmsg+0x13a/0x145
> [<ffffffff8150a93a>] ? inet_sendmsg+0x0/0x145
> [<ffffffff814a6d24>] sock_sendmsg+0xc0/0xd9
> [<ffffffff8106aad4>] ? lock_release_non_nested+0xe5/0x296
> [<ffffffff810c8fb0>] ? might_fault+0x68/0xb8
> [<ffffffff810c8fb0>] ? might_fault+0x68/0xb8
> [<ffffffff810c8ff9>] ? might_fault+0xb1/0xb8
> [<ffffffff810c8fb0>] ? might_fault+0x68/0xb8
> [<ffffffff814a6672>] ? move_addr_to_kernel+0x3f/0x56
> [<ffffffff814a7458>] sys_sendto+0xe0/0x108
> [<ffffffff810f9a76>] ? d_kill+0x6c/0x74
> [<ffffffff810e99df>] ? fput+0x1ce/0x1dd
> [<ffffffff81002c9b>] system_call_fastpath+0x16/0x1b
Hi Dimitris
Fix is known and under its way.
http://kerneltrap.org/mailarchive/linux-kernel/2010/9/23/4623037
Thanks !
prev parent reply other threads:[~2010-09-27 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 16:30 net-next rcu_dereference_check() warning Dimitris Michailidis
2010-09-27 16:45 ` 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=1285605912.3017.111.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=dm@chelsio.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