netdev - Re: [PATCH net-next 0/4] net: block BH in TCP callbacks

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: <20160519.113713.1974239749897301374.davem@davemloft.net>
Date:	Thu, 19 May 2016 11:37:13 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	edumazet@...gle.com
Cc:	netdev@...r.kernel.org, venkateshs@...gle.com,
	eric.dumazet@...il.com
Subject: Re: [PATCH net-next 0/4] net: block BH in TCP callbacks

From: Eric Dumazet <edumazet@...gle.com>
Date: Tue, 17 May 2016 17:44:05 -0700

> Four layers using TCP stack were assuming sk_callback_lock could
> be locked using read_lock() in their handlers because TCP stack
> was running with BH disabled.
> 
> This is no longer the case. Since presumably the rest could
> also depend on BH being disabled, just use read_lock_bh().
> 
> Then each layer might consider switching to RCU protection
> and no longer depend on BH.

Series applied, thanks Eric.