Re: lib/45564: 2nd socket created by socketpair(2) is not connected to 1st socket.

["NARUSE, Yui" <naruse%airemix.jp@localhost>]

The following reply was made to PR lib/45564; it has been noted by GNATS.

From: "NARUSE, Yui" <naruse%airemix.jp@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: lib/45564: 2nd socket created by socketpair(2) is not connected
 to 1st socket.
Date: Sun, 6 Nov 2011 07:28:29 +0900

 2011/11/5 Matthew Mondor <mm_lists%pulsar-zone.net@localhost>:
 > The following reply was made to PR lib/45564; it has been noted by GNATS.
 >
 > From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: lib/45564: 2nd socket created by socketpair(2) is not connec=
 ted
 > =A0to 1st socket.
 > Date: Sat, 5 Nov 2011 03:55:39 -0400
 >
 > =A0On Sat, =A05 Nov 2011 07:15:04 +0000 (UTC)
 > =A0"NARUSE, Yui" <naruse%airemix.jp@localhost> wrote:
 >
 > =A0> =A0No, it doesn't happen without SOCK_CLOEXEC.
 > =A0>
 > =A0> =A0Other operations like send also fails.
 > =A0> =A0Of course it works for first one.
 >
 > =A0I now looked at -current's sys_socketpair() in sys/kern/uipc_syscalls.=
 c:
 >
 > =A0Between 2011/06/26 and 2011/11/04 it seems that the call to
 > =A0soconnect2() is conditional upon:
 >
 > =A0SCARG(uap, type) =3D=3D SOCK_DGRAM
 >
 > =A0yet it should have been:
 >
 > =A0type =3D=3D SOCK_DGRAM
 >
 > =A0And this is the case with a very recent -current. =A0If you update aga=
 in,
 > =A0this probably has been fixed; please confirm if/when you can.
 
 I confirmed it is fixed now, thanks!
 
 --=20
 NARUSE, Yui =A0<naruse%airemix.jp@localhost>