From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 67751] Stack trace with suspicious RCU usage, when starting ovs-switchd
Date: Tue, 24 Jun 2014 09:53:55 +0000 [thread overview]
Message-ID: <bug-67751-28872-tyRVX4J3P2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-67751-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=67751
--- Comment #5 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
I just saw this again when I attempt to restart OpenvSwitch with Kernel --
3.16.0-0.rc1.git1.1.fc21.x86_64
---------------------
[ 9695.079715]
[ 9695.080492] ===============================
[ 9695.082559] [ INFO: suspicious RCU usage. ]
[ 9695.085105] 3.16.0-0.rc1.git1.1.fc21.x86_64 #1 Not tainted
[ 9695.088505] -------------------------------
[ 9695.090413] net/openvswitch/flow_table.c:255 suspicious
rcu_dereference_protected() usage!
[ 9695.094887]
[ 9695.094887] other info that might help us debug this:
[ 9695.094887]
[ 9695.100722]
[ 9695.100722] rcu_scheduler_active = 1, debug_locks = 0
[ 9695.105699] 1 lock held by ovs-vswitchd/1910:
[ 9695.108199] #0: (cb_lock){++++++}, at: [<ffffffff816f5159>]
genl_rcv+0x19/0x40
[ 9695.113083]
[ 9695.113083] stack backtrace:
[ 9695.115395] CPU: 0 PID: 1910 Comm: ovs-vswitchd Not tainted
3.16.0-0.rc1.git1.1.fc21.x86_64 #1
[ 9695.121638] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 9695.124076] 0000000000000000 000000002c60696c ffff8800b64ff968
ffffffff81807520
[ 9695.127732] ffff88029ce24d70 ffff8800b64ff998 ffffffff810fd7f7
0000000000000000
[ 9695.131321] ffff88029ccc6d20 ffff8800b64ffa90 ffff88029ccc6d00
ffff8800b64ff9b8
[ 9695.134931] Call Trace:
[ 9695.136158] [<ffffffff81807520>] dump_stack+0x4d/0x66
[ 9695.139031] [<ffffffff810fd7f7>] lockdep_rcu_suspicious+0xe7/0x120
[ 9695.141850] [<ffffffffa022abb0>] ovs_flow_tbl_destroy+0x60/0x70
[openvswitch]
[ 9695.145034] [<ffffffffa02247b1>] ovs_dp_cmd_new+0x311/0x4b0 [openvswitch]
[ 9695.148665] [<ffffffff816f621c>] genl_family_rcv_msg+0x1bc/0x3e0
[ 9695.152987] [<ffffffff81024369>] ? sched_clock+0x9/0x10
[ 9695.157925] [<ffffffff810e1afd>] ? sched_clock_local+0x1d/0x90
[ 9695.162486] [<ffffffff816f64c4>] genl_rcv_msg+0x84/0xc0
[ 9695.166797] [<ffffffff816f6440>] ? genl_family_rcv_msg+0x3e0/0x3e0
[ 9695.171411] [<ffffffff816f4b89>] netlink_rcv_skb+0xa9/0xd0
[ 9695.175809] [<ffffffff816f5168>] genl_rcv+0x28/0x40
[ 9695.179489] [<ffffffff816f4185>] netlink_unicast+0x125/0x1a0
[ 9695.184300] [<ffffffff816f455f>] netlink_sendmsg+0x35f/0x7d0
[ 9695.188510] [<ffffffff8169b57e>] sock_sendmsg+0x9e/0xe0
[ 9695.192580] [<ffffffff811f189e>] ? might_fault+0x5e/0xc0
[ 9695.196850] [<ffffffff811f18f9>] ? might_fault+0xb9/0xc0
[ 9695.200907] [<ffffffff811f189e>] ? might_fault+0x5e/0xc0
[ 9695.204862] [<ffffffff8169c5b8>] ___sys_sendmsg+0x408/0x420
[ 9695.208962] [<ffffffff8126ed5d>] ? __fget_light+0x13d/0x160
[ 9695.213088] [<ffffffff8126ed5d>] ? __fget_light+0x13d/0x160
[ 9695.217652] [<ffffffff8169cda1>] __sys_sendmsg+0x51/0x90
[ 9695.220513] [<ffffffff8169cdf2>] SyS_sendmsg+0x12/0x20
[ 9695.223422] [<ffffffff818110e9>] system_call_fastpath+0x16/0x1b
---------------------
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-06-24 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 9:49 [Bug 67751] New: Stack trace with suspicious RCU usage, when starting ovs-switchd bugzilla-daemon
2013-12-27 12:21 ` [Bug 67751] " bugzilla-daemon
2013-12-27 13:56 ` bugzilla-daemon
2013-12-27 14:32 ` bugzilla-daemon
2014-01-28 8:28 ` bugzilla-daemon
2014-01-31 16:25 ` bugzilla-daemon
2014-06-24 9:53 ` bugzilla-daemon [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=bug-67751-28872-tyRVX4J3P2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@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 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.