lwIP - A Lightweight TCP/IP stack - Bugs: bug #16390, Crash through adding and removing...
You are not allowed to post comments on this tracker with your current authentication level.
bug #16390: Crash through adding and removing tcb's to the TIME_WAIT list
Submitter: | None | ||
Submitted: | Thu 20 Apr 2006 04:22:49 AM UTC | ||
Category: | TCP | Severity: | 3 - Normal |
Item Group: | Crash Error | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | None |
Fri 21 Apr 2006 04:37:28 PM UTC, comment #1: |
Anonymous |
Thu 20 Apr 2006 04:22:49 AM UTC, original submission:
I had a problem when I did a heavy load test on a webserver with a multitasking os I programmed. The program hangs in the tcp_input function where it looks in the TIMED_WAIT list for connection that might get data now. Once there was only one tcp in the list and the ->next pointer was pointing to the tcp itselfe. An other time there were two connections in the list and the last points to the first.
|
Anonymous |
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 |
---|---|---|---|---|---|
2006-11-25 | christiaans | Status | None | Invalid | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
Ok i did some more investigations...
the problem occured also at the active list.
And it occures if you write or read to/from connection if a further write or read returns an error and is not handled. In my case it was a webserver application. I wrote and wrote and wrote without checking for errors because I thought the lower layers will handle it if there is a problem with writing to a connection in a "wrong" state. The problem occured if the client is resetting or closing the connection. The write give me an error and I didn't handle it and continued writing. After this point the tcb lists get meshed up.
I do error checking now and I am closing the connection if there is an error and everything works fine.