Re: kern/58874: nonblocking connect() and getsockname() error conditions

["Simon Burge via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Simon Burge <simonb%NetBSD.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/58874: nonblocking connect() and getsockname() error conditions
Date: Sun, 15 Dec 2024 16:27:26 +1100

 campbell+netbsd%mumble.net@localhost wrote:
 
 > Maybe both are sensible and compatible with POSIX -- I don't know, I
 > haven't assessed; I just stumbled upon the difference while running
 > git-cinnabar tests:
 >
 >   https://github.com/glandium/git-cinnabar/issues/340
 >
 > So I'm filing this PR to make a record of the difference and any
 > determination about it.
 >
 > [ test program deleted ]
 
 On FreeBSD 13.3:
 
 freebsd$ ./sn localhost 12345
 sn: first connect: Operation now in progress
 sn: second connect: Connection refused
 
 sn: connect SO_ERROR: No error: 0
 sn: third connect: Connection refused
 
 Cheers,
 Simon.