public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Cc: Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>
Subject: cgroups/netlink related rcu_dereference_check() without protection (2.6.35.4)
Date: Wed, 1 Sep 2010 21:43:37 -0400	[thread overview]
Message-ID: <20100902014337.GC30324@redhat.com> (raw)

I see this during boot on one of my boxes..

	Dave

INFO: suspicious rcu_dereference_check() usage. ]
---------------------------------------------------
include/linux/cgroup.h:542 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 swapper/1:
 #0:  (net_mutex){+.+.+.}, at: [<c074b595>] register_pernet_subsys+0x17/0x34

stack backtrace:
Pid: 1, comm: swapper Not tainted 2.6.35.4-15.fc14.i686.PAE #1
Call Trace:
 [<c07e2197>] ? printk+0x25/0x2e
 [<c0467969>] lockdep_rcu_dereference+0x7d/0x86
 [<c07440ea>] sock_update_classid+0x6c/0x8e
 [<c074416b>] sk_alloc+0x5f/0x6a
 [<c07674a9>] __netlink_create+0x2a/0x90
 [<c0768d54>] netlink_kernel_create+0x5f/0x14f
 [<c075805c>] rtnetlink_net_init+0x23/0x3b
 [<c0759412>] ? rtnetlink_rcv+0x0/0x27
 [<c074b388>] ops_init+0xda/0xe9
 [<c074b4c8>] register_pernet_operations+0x84/0xee
 [<c074b5a1>] register_pernet_subsys+0x23/0x34
 [<c0ab7e94>] rtnetlink_init+0x42/0xe0
 [<c0ab84fa>] netlink_proto_init+0xee/0x103
 [<c0ab840c>] ? netlink_proto_init+0x0/0x103
 [<c0403182>] do_one_initcall+0x62/0x170
 [<c0a809d3>] kernel_init+0x1b9/0x23a
 [<c0a8081a>] ? kernel_init+0x0/0x23a
 [<c0408fc2>] kernel_thread_helper+0x6/0x10


             reply	other threads:[~2010-09-02  1:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02  1:43 Dave Jones [this message]
2010-09-02  5:53 ` cgroups/netlink related rcu_dereference_check() without protection (2.6.35.4) Li Zefan

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=20100902014337.GC30324@redhat.com \
    --to=davej@redhat.com \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.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