[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #51937] Leaking tcp_pcbs on passive close with unacked

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #51937] Leaking tcp_pcbs on passive close with unacked data
Date: Mon, 4 Sep 2017 14:40:05 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36


                 Summary: Leaking tcp_pcbs on passive close with unacked data
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: goldsimon
            Submitted on: Mon 04 Sep 2017 06:40:03 PM UTC
                Category: TCP
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: goldsimon
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
            lwIP version: 2.0.2



When an application gets a FIN indication (recv callback with NULL pbuf) and
calls 'tcp_close()' from this callback when not having all received data ACKed
so far, the pcb can be leaked because it is removed from all pcb lists but the
check for freeing it delayed is not executed any more when unwinding the call

This is in since 2.0.0.

Suggested fix: move the "if (recv_flags & TF_CLOSED)" check in tcp_input()
further down.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]