netdev - Re: [PATCH net] openvswitch: fix a possible deadlock and lockdep warning

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] [day] [month] [year] [list]

Message-ID: <20140327125242.GA2475@t520.home>
Date:	Thu, 27 Mar 2014 09:52:42 -0300
From:	Flavio Leitner <fbl@...hat.com>
To:	netdev <netdev@...r.kernel.org>
Cc:	openvswitch <dev@...nvswitch.org>
Subject: Re: [PATCH net] openvswitch: fix a possible deadlock and lockdep
 warning

Please ignore this one.
I will repost with the correct openvswitch address.
Thanks

On Wed, Mar 26, 2014 at 09:56:12PM -0300, Flavio Leitner wrote:
> There are two problematic situations.
> 
> A deadlock can happen when is_percpu is false because it can get
> interrupted while holding the spinlock. Then it executes
> ovs_flow_stats_update() in softirq context which tries to get
> the same lock.
> 
> The second sitation is that when is_percpu is true, the code
> correctly disables BH only for the local CPU, but that confuses
> lockdep enough to trigger the warning below.
> 
> This patch disables BH for both cases fixing the real deadlock
> and the lockdep warning message.
[...]
 
--
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