[Top][All Lists]

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

[lwip-devel] [bug #50276] tcp: fix accept event on closed listening PCBs

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #50276] tcp: fix accept event on closed listening PCBs
Date: Tue, 28 Feb 2017 03:08:23 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Follow-up Comment #3, bug #50276 (project lwip):

Well spotted! And just in time for 2.0.2 :-)
I'd vote for solution 1) but just check state==SYN_RCVD (listener is only
available for TCP_LISTEN_BACKLOG with the event API). That way, the EVENT_API
gets more like the CALLBACK_API where an application doesn't know about the
new pcb before the accept callback.
BTW, there is a theoretical problem of the same kind in FIN_WAIT_1 state if
SYN_RCVD is closed, but since we don't pass a SYN_RCVD pcb to the application,
there's no way to close it. And in all situations where the stack internally
closes such a pcb, a RST is sent (so not resulting in FIN_WAIT_1).
Oh, and I think you should stay with the event API :-) Please ;-)


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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