lwip-devel
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible use

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible use of pcb with tcp_output()
Date: Mon, 21 Aug 2017 03:08:18 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 
Update of bug #51789 (project lwip):

                  Status:                    None => Invalid                
             Assigned to:                    None => goldsimon              
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

> TCP_EVENT_CLOSE

I assume you mean TCP_EVENT_CLOSED() ?

> which it does if pcb->recv is NULL

I don't see that.

> it is possible the tcp_close(pcb) will deallocate pcb if the pcb is in
certain states, like CLOSED

In general, it is possible that tcp_close deallocates the pcb. However, this
is done in states CLOSED, LISTEN and SYN_SENT only. There's no way a correct
FIN can be received in these states.

-> Invalid

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?51789>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/
reply via email to
[Prev in Thread] Current Thread [Next in Thread]