[lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself

[Sylvain Rochet]

Update of bug #63938 (project lwip):

                  Status:               Need Info => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #6:

You guessed wrong, calling netif->input() from interrupt context is obviously
a serious mistake unless lwIP runs entirely in interrupt context.

For pbuf allocation from other contexts, see SYS_LIGHTWEIGHT_PROT. For pbuf
de-allocation from other contexts (far less common than allocation though),
see LWIP_ALLOW_MEM_FREE_FROM_OTHER_CONTEXT.

Of course mutex locks are not called because you do not use an OS, the
contrary would be quite surprising.

And indeed, not returning ERR_ABRT when tcp_abort() was called is a documented
API misuse.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?63938>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/