netdev - Re: [PATCH net-next] sock: tigthen lockdep checks for sock_owned_by

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: <20160413.224336.614846243301591836.davem@davemloft.net>
Date:	Wed, 13 Apr 2016 22:43:36 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	netdev@...r.kernel.org, linux-cifs@...r.kernel.org,
	linux-bluetooth@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: [PATCH net-next] sock: tigthen lockdep checks for
 sock_owned_by_user

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Fri,  8 Apr 2016 15:11:27 +0200

> sock_owned_by_user should not be used without socket lock held. It seems
> to be a common practice to check .owned before lock reclassification, so
> provide a little help to abstract this check away.
> 
> Cc: linux-cifs@...r.kernel.org
> Cc: linux-bluetooth@...r.kernel.org
> Cc: linux-nfs@...r.kernel.org
> Signed-off-by: Hannes Frederic Sowa <hannes@...essinduktion.org>

Applied.