buglwIP - A Lightweight TCP/IP stack - Bugs: bug #47789, Hazard with netif_remove sending...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #47789: Hazard with netif_remove sending packets

Submitter:  Ambroz Bizjak <abizjak>
Submitted:  Tue 26 Apr 2016 06:53:14 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  Change Request Status:  Works For Me
Privacy:  Public Assigned to:  goldsimon
Open/Closed:  Closed Planned Release:  None
lwIP version:  git head

Tue 26 Apr 2016 07:43:17 PM UTC, comment #2: 

Yeah I see how sending these last packets might be useful.

Ambroz Bizjak <abizjak>
Tue 26 Apr 2016 07:37:06 PM UTC, comment #1: 

Hazard might not be the correct word here...

I think the current way is correct. If you can't send packets because the hardware is gone, don't send them.

There is a valid reason: if you only remove the lwIP netif but the actual connection could still be used, it's a good think to inform remote hosts that connections are aborted.

Simon Goldschmidt <goldsimon>
Group administrator
Tue 26 Apr 2016 06:53:14 PM UTC, original submission:  

Hey,
I've hit an issue in my application where I call netif_remove, and my code asserted because netif_remove tried to transmit packets, due to TCP connections being aborted. What do you think about ensuring within lwIP that this does nott happen? It will probably save a few applications with similar bugs lurking, and also I don't see any valid reason why packets would need to be sent to a netif that is being removed.

Ambroz Bizjak <abizjak>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by goldsimon (Posted a comment)
  • -email is unavailable- added by abizjak (Submitted the item)
  •  

    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
    2016-04-26 goldsimon StatusNone Works For Me
        Assigned toNone goldsimon
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code