lwIP - A Lightweight TCP/IP stack - Bugs: bug #57639, lwip_close or lwip_shutdown...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57639: lwip_close or lwip_shutdown doesn't cancel blocking lwip_recv
Submitter: | Benjamin K <bkausbk> | ||
Submitted: | Mon 20 Jan 2020 07:29:20 AM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Duplicate |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.1.1 |
Mon 20 Jan 2020 10:23:28 AM UTC, comment #3: |
Simon Goldschmidt <goldsimon> |
Mon 20 Jan 2020 10:06:57 AM UTC, comment #2: You said "it has been fixed long time ago" however the documentation for this option says contains the following statement:
|
Benjamin K <bkausbk> |
Mon 20 Jan 2020 08:19:16 AM UTC, comment #1: Sort of expected behaviour: to keep the footprint low, this is not supported by default.
|
Simon Goldschmidt <goldsimon> |
Mon 20 Jan 2020 07:29:20 AM UTC, original submission:
While in one task lwip_recv is waiting for new data (and is blocking) it is not possible to close/shutdown the socket from a second task, at least the task that is waiting will never stop waiting. In such case lwip_recev should leave blocking state and return 0 or -1. This is not the expected socket behaviour.
|
Benjamin K <bkausbk> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-01-20 | goldsimon | Status | None | Duplicate | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
That statement is outdated and will be removed before the next release. However, there's still at least one bug in there (bug 57445) that needs to be fixed.