buglwIP - 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

Submitted by:  Simon Goldschmidt <goldsimon>
Submitted on:  Tue 10 Feb 2015 09:01:49 PM UTC  
 
Category: sockets/netconnSeverity: 3 - Normal
Item Group: Faulty BehaviourStatus: Fixed
Privacy: PublicAssigned to: Simon Goldschmidt <goldsimon>
Open/Closed: ClosedPlanned Release: None
lwIP version: git head

Tue 10 Feb 2015 09:16:51 PM UTC, comment #1:

Fixed by adding a ~20 second timeout (SND_TIMEOUT is used if configured) unless linger is enabled.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
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).

There should be a timeout on this, I read about ~20 seconds in other implementations.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by goldsimon (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 10 Feb 2015 09:16:51 PM UTCgoldsimonStatusIn Progress=>Fixed
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1