Re: [ovs-dev] ovs inconsistent lock state

2014-03-03 Thread Jiri Pirko
Fri, Feb 28, 2014 at 08:21:35PM CET, zoltan.k...@citrix.com wrote: >I also had problems with these locks on current net-next, I believe >the issue is that "datapath: Fix deadlock during stats update." is >not merged from official OVS repo to kernel. Nope. I tried the patch and I'm still getting th

Re: [ovs-dev] ovs inconsistent lock state

2014-02-28 Thread Zoltan Kiss
I also had problems with these locks on current net-next, I believe the issue is that "datapath: Fix deadlock during stats update." is not merged from official OVS repo to kernel. Zoli On 13/02/14 17:13, Jiri Pirko wrote: Hi. On current net-next I'm getting following message once I add a dp:

Re: [ovs-dev] ovs inconsistent lock state

2014-02-13 Thread David Miller
From: Jiri Pirko Date: Thu, 13 Feb 2014 21:07:53 +0100 > Thu, Feb 13, 2014 at 08:26:54PM CET, da...@davemloft.net wrote: >>From: Jiri Pirko >>Date: Thu, 13 Feb 2014 19:12:57 +0100 >> > [ 3014.524118] [] ? __dev_queue_xmit+0x5/0x6a0 >> ... >>> I fail to see where bh is disabled. ovs_dp_proc

Re: [ovs-dev] ovs inconsistent lock state

2014-02-13 Thread Jiri Pirko
Thu, Feb 13, 2014 at 08:26:54PM CET, da...@davemloft.net wrote: >From: Jiri Pirko >Date: Thu, 13 Feb 2014 19:12:57 +0100 > [ 3014.524118] [] ? __dev_queue_xmit+0x5/0x6a0 > ... >> I fail to see where bh is disabled. ovs_dp_process_received_packet() is >> called with rcu_read_lock... > >It ha

Re: [ovs-dev] ovs inconsistent lock state

2014-02-13 Thread David Miller
From: Jiri Pirko Date: Thu, 13 Feb 2014 19:12:57 +0100 >>> [ 3014.524118] [] ? __dev_queue_xmit+0x5/0x6a0 ... > I fail to see where bh is disabled. ovs_dp_process_received_packet() is > called with rcu_read_lock... It happens in __dev_queue_xmit(), which does rcu_read_lock_bh(). _

Re: [ovs-dev] ovs inconsistent lock state

2014-02-13 Thread Pravin Shelar
On Thu, Feb 13, 2014 at 10:12 AM, Jiri Pirko wrote: > Thu, Feb 13, 2014 at 06:42:03PM CET, pshe...@nicira.com wrote: >>On Thu, Feb 13, 2014 at 9:13 AM, Jiri Pirko wrote: >>> Hi. >>> >>> On current net-next I'm getting following message once I add a dp: >>> >>> [ 3014.523665] =

Re: [ovs-dev] ovs inconsistent lock state

2014-02-13 Thread Jiri Pirko
Thu, Feb 13, 2014 at 06:42:03PM CET, pshe...@nicira.com wrote: >On Thu, Feb 13, 2014 at 9:13 AM, Jiri Pirko wrote: >> Hi. >> >> On current net-next I'm getting following message once I add a dp: >> >> [ 3014.523665] = >> [ 3014.524118] [ INFO: inconsistent lock stat

Re: [ovs-dev] ovs inconsistent lock state

2014-02-13 Thread Pravin Shelar
On Thu, Feb 13, 2014 at 9:13 AM, Jiri Pirko wrote: > Hi. > > On current net-next I'm getting following message once I add a dp: > > [ 3014.523665] = > [ 3014.524118] [ INFO: inconsistent lock state ] > [ 3014.524118] 3.14.0-rc2+ #1 Not tainted > [ 3014.524118] -

[ovs-dev] ovs inconsistent lock state

2014-02-13 Thread Jiri Pirko
Hi. On current net-next I'm getting following message once I add a dp: [ 3014.523665] = [ 3014.524118] [ INFO: inconsistent lock state ] [ 3014.524118] 3.14.0-rc2+ #1 Not tainted [ 3014.524118] - [ 3014.524118] inconsistent {SOFTIRQ-