netdev - Re: [RFC] nasty corner case in unix_dgram

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

Message-ID: <878sy2k1m3.fsf@doppelsaurus.mobileactivedefense.com>
Date:   Tue, 26 Feb 2019 15:31:32 +0000
From:   Rainer Weikusat <rweikusat@...ktalk.net>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     Jason Baron <jbaron@...mai.com>, netdev@...r.kernel.org
Subject: Re: [RFC] nasty corner case in unix_dgram_sendmsg()

Al Viro <viro@...iv.linux.org.uk> writes:
> On Tue, Feb 26, 2019 at 06:28:17AM +0000, Al Viro wrote:

[...]


>> 	* if after relocking we see that unix_peer(sk) now
>> is equal to other, we arrange for wakeup forwarding from other's
>> peer_wait *and* if that has (likely) succeeded we fail with -EAGAIN.
>> Huh?

This returns 1 if sending isn't possible at the moment, ie, if the
process which tries to send has to wait.