[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: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #46701] Non-standard close behavior can result in socket/netconn leaks |
Date: |
Thu, 17 Mar 2016 19:52:05 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 |
Update of bug #46701 (project lwip):
Status: None => In Progress
Assigned to: None => goldsimon
_______________________________________________________
Follow-up Comment #6:
Reading up on this, you're probably right that lwIP-internal resource shortage
should not lead to EWOULDBLOCK on socket layer. I'm OK with changing the
netconn API in this respect, too.
I'll change the code to fix this 1st bug. However, there might be
However, deleting the netconn & socket in all 'err != ERR_OK' cases is
definitively wrong and can lead to pcb leaks (instead of the netconn/socket
leaks you want to fix).
So why don't we solve this 2nd bug by returning ERR_OK when from 'err_tcp()'
(which is called on RST) if 'old_state == NETCONN_CLOSE' ? Noone is interested
in the RST in this case anyway.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?46701>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.nongnu.org/