netdev - Re: ovs inconsistent lock state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20140213.152314.1937497665232682958.davem@davemloft.net>
Date:	Thu, 13 Feb 2014 15:23:14 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jiri@...nulli.us
Cc:	pshelar@...ira.com, netdev@...r.kernel.org, jesse@...ira.com,
	dev@...nvswitch.org
Subject: Re: ovs inconsistent lock state

From: Jiri Pirko <jiri@...nulli.us>
Date: Thu, 13 Feb 2014 21:07:53 +0100

> Thu, Feb 13, 2014 at 08:26:54PM CET, davem@...emloft.net wrote:
>>From: Jiri Pirko <jiri@...nulli.us>
>>Date: Thu, 13 Feb 2014 19:12:57 +0100
>>
>>>>> [ 3014.524118]  [<ffffffff815eb585>] ? __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().
> 
> On tx yes. But how about rx? I don't see it there (rx_handler path).
> Maybe I'm missing something.

For this code path they are one in the same.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html