[lwip-devel] [bug #49684] lwip_netconn_do_writemore(): non-blocking ERR_MEM treated as failure

[Joel Cunningham]

Update of bug #49684 (project lwip):

                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

Simon,

I agree with you that using sent_tcp/poll_tcp to check if the socket is
writable again after a memory allocation failure could lead to some false
positives because snd_buf/snd_queuelen doesn't necessarily have anything to do
with the free space in the memory pools.

For my particular use case, sent_tcp is triggering the socket as writable
again and my TCP segments are composed for PBUF_RAM and TCP_SEG allocations. 
At least one of these segments is freed when sent_tcp is called

Also, as mentioned in the original description, this is the same approach that
blocking sockets uses, so the limitation exists there as well.

Committed in 5030fa81a020280c467126568027608fa08e5136


    _______________________________________________________

Reply to this item at:

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

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