lwIP - A Lightweight TCP/IP stack - Bugs: bug #28605, Write can block when cable...
You are not allowed to post comments on this tracker with your current authentication level.
bug #28605: Write can block when cable unplugged
Submitter: | TabascoEye <tabascoeye> | ||
Submitted: | Thu 14 Jan 2010 11:21:30 AM UTC | ||
Category: | TCP | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | Other |
Wed 27 Jan 2010 06:26:42 PM UTC, comment #5: |
Simon Goldschmidt <goldsimon> |
Sat 23 Jan 2010 02:52:57 PM UTC, comment #4: Since the '+2' was not really satisfying, I've created a patch (against CVS head), that adds an option TCP_SNDQUEUELOWAT much like TCP_SNDLOWAT but for pcb->snd_queuelen.
|
Simon Goldschmidt <goldsimon> |
Fri 15 Jan 2010 04:54:57 PM UTC, comment #3: Oh, now I see what you are getting at. So your change only makes sense when using select() to see which socket is writable? (I didn't get that from the initial post of the summary).
|
Simon Goldschmidt <goldsimon> |
Fri 15 Jan 2010 01:09:37 PM UTC, comment #2: This scenario is basically an extension of the SNDLOWAT scenario. And in both cases we want to send the APIMSG to signal to select() that the write_FD should be reset because the next write() will block.
|
TabascoEye <tabascoeye> |
Thu 14 Jan 2010 08:14:25 PM UTC, comment #1: Could you go a bit more in detail why calling the API_EVENT in that case helps? I would have thought we might want to abort the write with 'failed' in this case, but that's kind of risky when part of the data has already been sent...
|
Simon Goldschmidt <goldsimon> |
Thu 14 Jan 2010 11:21:30 AM UTC, original submission:
When doing netconn_write, the codeflow goes through do_write, do_writemore, tcp_write, tcp_enqueue.
|
TabascoEye <tabascoeye> |
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 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-01-27 | goldsimon | Open/Closed | Open | Closed | |
2010-01-27 | goldsimon | Status | In Progress | Fixed | |
2010-01-23 | goldsimon | Status | None | In Progress | |
Assigned to | None | goldsimon | |||
2010-01-23 | goldsimon | Attached File | - | Added lwip_bug_28605.patch, #19537 | |
2010-01-15 | tabascoeye | Attached File | - | Added lwip.patch, #19493 |
Powered by Savane 3.13-02a9.
Corresponding source code
Checked in as noon disagreed...