linux-kernel - Re: [PATCH v4] net: sock: move ->sk

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: <20160520.180552.293412690344388226.davem@davemloft.net>
Date:	Fri, 20 May 2016 18:05:52 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	aryabinin@...tuozzo.com
Cc:	hannes@...essinduktion.org, rweikusat@...ileactivedefense.com,
	edumazet@...gle.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] net: sock: move ->sk_shutdown out of bitfields.

From: Andrey Ryabinin <aryabinin@...tuozzo.com>
Date: Wed, 18 May 2016 19:19:27 +0300

> ->sk_shutdown bits share one bitfield with some other bits in sock struct,
> such as ->sk_no_check_[r,t]x, ->sk_userlocks ...
> sock_setsockopt() may write to these bits, while holding the socket lock.
> 
> In case of AF_UNIX sockets, we change ->sk_shutdown bits while holding only
> unix_state_lock(). So concurrent setsockopt() and shutdown() may lead
> to corrupting these bits.
> 
> Fix this by moving ->sk_shutdown bits out of bitfield into a separate byte.
> This will not change the 'struct sock' size since ->sk_shutdown moved into
> previously unused 16-bit hole.
> 
> Signed-off-by: Andrey Ryabinin <aryabinin@...tuozzo.com>
> Suggested-by: Hannes Frederic Sowa <hannes@...essinduktion.org>

Looks good, applied and queued up for -stable.

Thanks.