lwIP - A Lightweight TCP/IP stack - Bugs: bug #23119, After a read with timeout, the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #23119: After a read with timeout, the socket is unuseable
| Submitter: | Robert Reither <nathan2225> | ||
| Submitted: | Wed 30 Apr 2008 01:38:32 PM UTC | ||
| Category: | sockets/netconn | Severity: | 3 - Normal |
| Item Group: | Change Request | Status: | Fixed |
| Privacy: | Public | Assigned to: | jifl |
| Open/Closed: | Closed | Planned Release: | None |
| lwIP version: | None | ||
Jump to the original submission
|
Fri 09 May 2008 12:15:04 PM UTC, comment #13: |
Jonathan Larmour <jifl> |
|
Sun 04 May 2008 07:46:09 PM UTC, comment #12: Ok, it's fine for me. I will do more tests tomorrow with some tcp apps, but it's ok for contrib/apps modules (based only on udp/raw). |
Frédéric Bernon <fbernon> |
|
Thu 01 May 2008 06:02:33 PM UTC, comment #11:
|
Simon Goldschmidt <goldsimon> |
|
Thu 01 May 2008 03:34:37 PM UTC, comment #10: Updated patch as per Frederic's comment #9. Frederic says he'll test it over the weekend, so all being well, I'll check in on Monday.
|
Jonathan Larmour <jifl> |
|
Thu 01 May 2008 02:47:51 PM UTC, comment #9: hi,
|
Frédéric Bernon <fbernon> |
|
Thu 01 May 2008 02:32:20 PM UTC, comment #8: I am using the api calls and things are working as expected using the supplied patch. The previous timeout error doesn't error out netconn_write() anymore.
|
Dustin Stahlback <dstahlback> |
|
Thu 01 May 2008 01:56:22 PM UTC, comment #7: Dustin, actually the patch I'm attaching should do the work. Is someone prepared to test it?
|
Jonathan Larmour <jifl> |
|
Thu 01 May 2008 01:31:57 PM UTC, comment #6: This issue has affected me also, is the fix to have ERR_IS_FATAL act as :
|
Dustin Stahlback <dstahlback> |
|
Thu 01 May 2008 11:57:58 AM UTC, comment #5: Looks good, declaring this error as NON_FATAL and resetting
|
Robert Reither <nathan2225> |
|
Thu 01 May 2008 08:12:10 AM UTC, comment #4: Read timeouts should not be fatal. |
Kieran Mansley <kieranm> |
|
Wed 30 Apr 2008 08:08:18 PM UTC, comment #3: I think the only change should be in err.h, where ERR_TIMEOUT must be move upwards a bit, so that the ERR_IS_FATAL check leads to 0 for ERR_TIMEOUT instead of 1 as it is now.
|
Simon Goldschmidt <goldsimon> |
|
Wed 30 Apr 2008 05:18:24 PM UTC, comment #2: I don't remember the discussion, so for all I know this is contrary to anything I may or may not have said before :-), but as described in this bug, the timeout should not be fatal.
|
Jonathan Larmour <jifl> |
|
Wed 30 Apr 2008 04:13:26 PM UTC, comment #1: Oh, look, someone is actually using the socket read timeout ;-)
|
Simon Goldschmidt <goldsimon> |
|
Wed 30 Apr 2008 01:38:32 PM UTC, original submission:
|
Robert Reither <nathan2225> |
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 8 latest changes.
| Date | Changed by | Updated Field | Previous Value | => | Replaced by |
|---|---|---|---|---|---|
| 2008-05-09 | jifl | Status | Confirmed | Fixed | |
| Open/Closed | Open | Closed | |||
| 2008-05-01 | jifl | Attached File | - | Added lwip.bug23119.2.patch, #15576 | |
| 2008-05-01 | jifl | Attached File | #15571 | Removed | |
| 2008-05-01 | jifl | Attached File | - | Added lwip.bug23119.patch, #15571 | |
| Assigned to | None | jifl | |||
| 2008-04-30 | goldsimon | Item Group | None | Change Request | |
| Status | None | Confirmed |

I've checked the patch in now.