[lwip-devel] [bug #19162] lwip_sendto: possible to corrupt remote addr/port connection state

[Simon Goldschmidt]

Follow-up Comment #26, bug #19162 (project lwip):

To this general discussion: how do we go on with this? I think this is a big
bug regarding thread-safety (and speed).

In contrast to patch file #12448, I'd rather somehow include the struct
sockaddr, but that would include socket-structs in netconn-api so that would
be bad. In that case, we could stick to port==0 = send, port != 0 = sendto.

I did not test the patch in detail, maybe I can give some detailed comment on
it next week. But overall, I think it's going into the right direction
(although we should take care it doesn't slow down sends on connected sockets
too much).


    _______________________________________________________

Reply to this item at:

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

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