[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #46701] Non-standard close behavior can result in sock
|
From: |
Joel Cunningham |
|
Subject: |
[lwip-devel] [bug #46701] Non-standard close behavior can result in socket/netconn leaks |
|
Date: |
Wed, 16 Dec 2015 23:05:31 +0000 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 |
Follow-up Comment #1, bug #46701 (project lwip):
Here's the Steven's text, apologies for messed up formatting:
The default action of close with a TCP socket is to mark the socket
as closed and return to the process immediately. The socket descriptor
is no longer usable by the process: It cannot be used as an argument to
read or write. But, TCP will try to send any data that is already queued
to be sent to the other end, and after this occurs, the normal TCP
connection termination sequence takes place.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?46701>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/