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: Sun, 02 Dec 2007 16:42:13 +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

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

                 Summary: segment leak in ooseq processing when last data
packet was lost
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: goldsimon
            Submitted on: Sonntag 02.12.2007 um 16:42
                Category: TCP
                Severity: 3 - Normal
              Item Group: Crash Error
                  Status: Confirmed
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 

    _______________________________________________________

Details:

See this mail from Thomas Catalino for a detailed description:
http://lists.nongnu.org/archive/html/lwip-users/2007-12/msg00003.html

scenario: the last data packet (not containing FIN) is lost and the FIN
packet (not containing data) is put on ooseq. Then the data packet is
retransmitted *with* FIN. ooseq handling in tcp_receive processes trimming of
segments but does not correctly handle this case (since data length is not
affected but sequence numbers are).

It is detected that there is something do trim (in tcp_receive, line 1016),
but no real action is taken).

This results in the first received FIN segment leaking.




    _______________________________________________________

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]