All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 27 Dec 2013 13:56:35 +0000	[thread overview]
Message-ID: <bug-67751-28872-etqPpyYQvA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-67751-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=67751

Kashyap Chamarthy <kashyap.cv@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|3.13-rc4                    |3.13.0-0.rc4.git5.1.fc21.x8
                   |                            |6_64

--- Comment #1 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
Just to note this is reproducible, I ran into it again when I booted the VM
through its serial console:

---------------------
.
.
.
[  OK  ] Started RPC bind service.
[   23.707895] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   24.460881] gre: GRE over IPv4 demultiplexor driver
[   24.534446] openvswitch: Open vSwitch switching datapath
[   24.764568] device ovs-system entered promiscuous mode
[   25.109235] device br-int entered promiscuous mode
[   25.121450] 
[   25.122468] ===============================
[   25.124704] [ INFO: suspicious RCU usage. ]
[   25.126644] 3.13.0-0.rc4.git5.1.fc21.x86_64 #1 Not tainted
[   25.129110] -------------------------------
[   25.132497] net/openvswitch/flow_table.c:436 suspicious
rcu_dereference_check() usage!
[   25.135792] 
[   25.135792] other info that might help us debug this:
[   25.135792] 
[   25.139221] 
[   25.139221] rcu_scheduler_active = 1, debug_locks = 0
[   25.142044] 2 locks held by ovs-vswitchd/719:
[   25.143934]  #0:  (cb_lock){++++++}, at: [<ffffffff816535c9>]
genl_rcv+0x19/0x40
[   25.148294]  #1:  (ovs_mutex){+.+.+.}, at: [<ffffffffa01aedc9>]
ovs_flow_cmd_new_or_set+0xf9/0x600 [openvswitch]
[   25.153885] 
[   25.153885] stack backtrace:
[   25.156553] CPU: 10 PID: 719 Comm: ovs-vswitchd Not tainted
3.13.0-0.rc4.git5.1.fc21.x86_64 #1
[   25.162587] Hardware name: Red Hat KVM, BIOS Bochs 01/01/2011
[   25.165237]  0000000000000001 ffff8800370877e0 ffffffff8175b6d2
ffff880499f60000
[   25.169376]  ffff880037087810 ffffffff810cd2f7 ffff88049bfb1260
ffff88003708787c
[   25.175682]  ffff8800daaa7d68 ffff8800daaa7d48 ffff880037087860
ffffffffa01b6608
[   25.180373] Call Trace:
[   25.181540]  [<ffffffff8175b6d2>] dump_stack+0x4d/0x66
[   25.183970]  [<ffffffff810cd2f7>] lockdep_rcu_suspicious+0xe7/0x120
[   25.186854]  [<ffffffffa01b6608>] ovs_flow_tbl_lookup+0x188/0x1b0
[openvswitch]
[   25.189780]  [<ffffffffa01aee06>] ovs_flow_cmd_new_or_set+0x136/0x600
[openvswitch]
[   25.193182]  [<ffffffff816552c1>] ? genl_family_rcv_msg+0x2c1/0x370
[   25.195832]  [<ffffffff8165518d>] genl_family_rcv_msg+0x18d/0x370
[   25.198584]  [<ffffffff81655370>] ? genl_family_rcv_msg+0x370/0x370
[   25.201229]  [<ffffffff816553fe>] genl_rcv_msg+0x8e/0xd0
[   25.203439]  [<ffffffff81653079>] netlink_rcv_skb+0xa9/0xc0
[   25.205736]  [<ffffffff816535d8>] genl_rcv+0x28/0x40
[   25.207802]  [<ffffffff816526a5>] netlink_unicast+0xd5/0x1a0
[   25.210136]  [<ffffffff81652aa7>] netlink_sendmsg+0x337/0x750
[   25.212643]  [<ffffffff81600cab>] sock_sendmsg+0x8b/0xc0
[   25.214964]  [<ffffffff811a7dbf>] ? might_fault+0x5f/0xb0
[   25.217209]  [<ffffffff811a7e08>] ? might_fault+0xa8/0xb0
[   25.219443]  [<ffffffff811a7dbf>] ? might_fault+0x5f/0xb0
[   25.221785]  [<ffffffff81610a5e>] ? verify_iovec+0x5e/0xe0
[   25.224309]  [<ffffffff81601109>] ___sys_sendmsg+0x3d9/0x3f0
[   25.227001]  [<ffffffff810575e7>] ? kvm_clock_read+0x27/0x40
[   25.229696]  [<ffffffff81021a59>] ? sched_clock+0x9/0x10
[   25.232047]  [<ffffffff810b64cd>] ? sched_clock_local+0x1d/0x80
[   25.235062]  [<ffffffff810b6658>] ? sched_clock_cpu+0xa8/0x100
[   25.238061]  [<ffffffff810cb4cd>] ? trace_hardirqs_off+0xd/0x10
[   25.240594]  [<ffffffff810b679f>] ? local_clock+0x5f/0x70
[   25.243667]  [<ffffffff810cc07f>] ? lock_release_holdtime.part.29+0xf/0x190
[   25.246875]  [<ffffffff8121c85d>] ? fget_light+0xed/0x4f0
[   25.249346]  [<ffffffff8121c7ac>] ? fget_light+0x3c/0x4f0
[   25.252287]  [<ffffffff81602662>] __sys_sendmsg+0x42/0x80
[   25.254691]  [<ffffffff816026b2>] SyS_sendmsg+0x12/0x20
[   25.257184]  [<ffffffff8176e329>] system_call_fastpath+0x16/0x1b
[   25.359076] device br-tun entered promiscuous mode

Fedora release 20 (Heisenbug)
Kernel 3.13.0-0.rc4.git5.1.fc21.x86_64 on an x86_64 (ttyS0)
---------------------

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-12-27 13:56 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 [this message]
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

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-etqPpyYQvA@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.