netdev - Re: [PATCH] af_unix: Only allow recv on connected seqpacket sockets.

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: <20110501.231649.71121140.davem@davemloft.net>
Date:	Sun, 01 May 2011 23:16:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ebiederm@...ssion.com
Cc:	netdev@...r.kernel.org, xemul@...nvz.org, dan@...ni.org,
	stable@...nel.org
Subject: Re: [PATCH] af_unix: Only allow recv on connected seqpacket
 sockets.

From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Mon, 25 Apr 2011 07:26:27 -0700

> When the other socket in an established connection calls unix_shutdown
> or unix_release_sock.  sk->sk_shutdown is changed, but sk_state is
> left at TCP_ESTABLISHED.  Therefore we do not need a special
> case in unix_seqpacket_recvmsg to handle the RCV_SHUTDOWN case
> because in any case where that applies we will be in TCP_ESTABLISHED
> and we will simply call unix_dgram_recvmsg.

Thanks for explaining Eric, patch applied.
--
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