[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #52112] Unavoidable hazards when calling tcp_close fro

From: Ambroz Bizjak
Subject: [lwip-devel] [bug #52112] Unavoidable hazards when calling tcp_close from callback
Date: Mon, 25 Sep 2017 15:21:01 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Follow-up Comment #1, bug #52112 (project lwip):

I see that lwIP avoids freeing the PCB from tcp_close when called from
tcp_input, so the correct approach is to return ERR_ABRT if and only if the
application called tcp_abort. I must have seen the "tcp_close freeing PCB"
issue with an older lwIP version and chose to return ERR_ABRT whenever I
called tcp_close and this became broken with newer lwIP.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]