lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] [bug #21699] segment leak in ooseq processing when last dat


From: Simon Goldschmidt
Subject: [lwip-devel] [bug #21699] segment leak in ooseq processing when last data packet was lost
Date: Mon, 03 Dec 2007 21:06:20 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Follow-up Comment #1, bug #21699 (project lwip):

It seems that not only the ooseq processing has a problem (in fact, that is
not really a problem).

In the scenario below, tcp_pcb_remove is called before freeing the pcb ('if
(recv_flags & TF_CLOSED)' in tcp_input), which should free all the lists.
However, tcp_pcb_purge (called from tcp_pcb_remove) does nothing in the CLOSED
state (as well as in the TIME_WAIT state). Changing this check solves this
bug.

Therefore, I would rather solve the bug that way instead of checking the
ooseq for flags (like FIN) that are received twice (the code would be more
complex there). But maybe that is not the cleanest thing to do?

Any lwIP TCP experts have to say something about this? Kieran?

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/





reply via email to

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