[lwip-devel] [bug #31748] Calling non-blocking connect more than once can render a socket useless

[Yoav]

URL:
  <http://savannah.nongnu.org/bugs/?31748>

                 Summary: Calling non-blocking connect more than once can
render a socket useless
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: djinng
            Submitted on: Thu 02 Dec 2010 01:49:40 PM GMT
                Category: sockets
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: CVS Head

    _______________________________________________________

Details:

If connect is called again while a previous non-blocking connect is being
processed, ERR_ISCONN is assigned to conn->err.

1. Now, if the connection succeeds, do_connected will not be able to set
conn->err to ERR_OK since it checks for ERR_INPROGRESS.

2. To make things worse, ERR_ISCONN is treated as a FATAL error, and will
therefore render the socket unusable.

3. According to Posix, EALREADY should be returned while a connect is in
progress, and EISCONN should be returned when a socket is connected.

4. err_to_errno(ERR_ISCONN) translates to -1 instead of a valid code (e.g
EISCONN)





    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?31748>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/