lwIP - A Lightweight TCP/IP stack - Bugs: bug #44225, closing TCP socket should time out...
You are not allowed to post comments on this tracker with your current authentication level.
bug #44225: closing TCP socket should time out eventually
Submitter: | Simon Goldschmidt <goldsimon> | ||
Submitted: | Tue 10 Feb 2015 09:01:49 PM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Tue 10 Feb 2015 09:16:51 PM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Tue 10 Feb 2015 09:01:49 PM UTC, original submission:
There are currently (rare) situations where closing TCP sockets can need long or never finish because on memory error or when the remote host never ACKs the last segment, close is just retried forever (in the tcp poll callback).
|
Simon Goldschmidt <goldsimon> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-02-10 | goldsimon | Status | In Progress | Fixed | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
Fixed by adding a ~20 second timeout (SND_TIMEOUT is used if configured) unless linger is enabled.