[lwip-devel] [bug #46701] Non-standard close behavior can result in socket/netconn leaks

[Simon Goldschmidt]

Follow-up Comment #4, bug #46701 (project lwip):

I can follow you on Stevens, but he doesn't talk about nonblocking sockets or
is he? I don't know if we're doing something wrong here or not.

By making nonblocking sockets behave like blocking sockets, you lose the
nonblocking thing, so it might be better to let close return and set a flag in
the netconn to dealloc on close success (and yes, always dealloc the socket in
close()).

I'm not sure I can follow you on comment #2 though.

The patch in comment #3 seems to dealloc socket/netconn too early without
freeing the pcb... or am I wrong?

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.nongnu.org/