[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: lib/45564: 2nd socket created by socketpair(2) is not connected to 1st socket.
The following reply was made to PR lib/45564; it has been noted by GNATS.
From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
Subject: Re: lib/45564: 2nd socket created by socketpair(2) is not connected
to 1st socket.
Date: Sat, 5 Nov 2011 03:55:39 -0400
On Sat, 5 Nov 2011 07:15:04 +0000 (UTC)
"NARUSE, Yui" <naruse%airemix.jp@localhost> wrote:
> No, it doesn't happen without SOCK_CLOEXEC.
> Other operations like send also fails.
> Of course it works for first one.
I now looked at -current's sys_socketpair() in sys/kern/uipc_syscalls.c:
Between 2011/06/26 and 2011/11/04 it seems that the call to
soconnect2() is conditional upon:
SCARG(uap, type) == SOCK_DGRAM
yet it should have been:
type == SOCK_DGRAM
And this is the case with a very recent -current. If you update again,
this probably has been fixed; please confirm if/when you can.
Main Index |
Thread Index |