MFC rev 1.89DragonFly_RELEASE_1_12
commit76797d8b4e9ecbad253403f9fb5853041c4fa960
authorSepherosa Ziehau <sephe@dragonflybsd.org>
Sat, 26 Jul 2008 15:46:18 +0000 (26 15:46 +0000)
committerSepherosa Ziehau <sephe@dragonflybsd.org>
Sat, 26 Jul 2008 15:46:18 +0000 (26 15:46 +0000)
tree43a0d359ba4f28add2dbe7da888581cf3b82e02c
parentf030f389711efaec37bed03a8fa86a3f117efecf
MFC rev 1.89
  Bring following change from FreeBSD (yar@freebsd.org):
    uipc_syscall.c rev 1.154

    If connect(2) has been interrupted by a signal and therefore the
    connection is to be established asynchronously, behave as in the
    case of non-blocking mode:

    - keep the SS_ISCONNECTING bit set thus indicating that
      the connection establishment is in progress, which is the case
      (clearing the bit in this case was just a bug);

    - return EALREADY, instead of the confusing and unreasonable
      EADDRINUSE, upon further connect(2) attempts on this socket
      until the connection is established (this also brings our
      connect(2) into accord with IEEE Std 1003.1.)

Tested-by: y0netan1@
Reviewed-by: hsu@
  Dragonfly-bug: <http://bugs.dragonflybsd.org/issue1079>
sys/kern/uipc_syscalls.c