tcp_close.c:when tcp socket stays in TCP_FIN_WAIT_1 or TCP_FIN_WAIT_2…

…,calling tcp_close_eventhandler releases received packets when tcp socket stays in TCP_FIN_WAIT_1 or TCP_FIN_WAIT_2,not actively calling tcp_close_eventhandler,can reuslt in some TCP socket being set to a closed state,but nofosegs are not directly released,leading to IOB resource leakage. Signed-off-by: wangchen <[email protected]>
wangchen61698 · Aug 26, 2024 · 4ff01ba · 4ff01ba
1 parent 4d4d8a6
commit 4ff01ba
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/net/tcp/tcp_input.c b/net/tcp/tcp_input.c
@@ -1616,6 +1616,12 @@ static void tcp_input(FAR struct net_driver_s *dev, uint8_t domain,
              */
 
             conn->tcpstateflags = TCP_CLOSED;
+
+            /* In the TCP_FIN_WAIT_1, we need call tcp_close_eventhandler to
+             * release nofosegs, that we received in this state.
+             */
+
+            tcp_callback(dev, conn, TCP_CLOSE);
             tcp_reset(dev, conn);
             return;
           }
@@ -1649,6 +1655,12 @@ static void tcp_input(FAR struct net_driver_s *dev, uint8_t domain,
              */
 
             conn->tcpstateflags = TCP_CLOSED;
+
+            /* In the TCP_FIN_WAIT_2, we need call tcp_close_eventhandler to
+             * release nofosegs, that we received in this state.
+             */
+
+            tcp_callback(dev, conn, TCP_CLOSE);
             tcp_reset(dev, conn);
             return;
           }