lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] [bugs #11400] ARP multi-packet-queue modifies TCP unsent/un


From: Leon Woestenberg
Subject: [lwip-devel] [bugs #11400] ARP multi-packet-queue modifies TCP unsent/unacked segment packet pbuf chain into packet queue
Date: Mon, 03 Jan 2005 13:17:35 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

This mail is an automated notification from the bugs tracker
 of the project: lwIP - A Lightweight TCP/IP stack.

/**************************************************************************/
[bugs #11400] Latest Modifications:

Changes by: 
                Leon Woestenberg <address@hidden>
'Date: 
                Mon 01/03/2005 at 18:05 (Europe/Amsterdam)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Postponed


------------------ Additional Follow-up Comments ----------------------------
Bug is reported to dissappear when the ARP queueing is limited to one packet 
per entry, so I limited the implementation to that. That fixes the bug, but 
leaves future work to see if a multi-packet queue can be implemented neatly.






/**************************************************************************/
[bugs #11400] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=11400>
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: Leon Woestenberg
On: Sun 12/26/2004 at 15:52

Category:  ARP
Severity:  5 - Average
Item Group:  Faulty Behaviour
Resolution:  Postponed
Privacy:  Public
Assigned to:  leonwoestenberg
Status:  Open


Summary:  ARP multi-packet-queue modifies TCP unsent/unacked segment packet 
pbuf chain into packet queue

Original Submission:  When multiple packets are queued on one ARP entry, the 
first packet has a next pointer pointing to the next packet. 

However, if this was a queued TCP segment, we are modifying it, without TCP 
knowing about this.

Possible solutions: disallow multiple packets on the ARP queue, or modify TCP 
to know about packet queues.

Optimal solution is probably to design a seperate struct for ARP queues, much 
like the 'struct tcp_seg' linked list.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Mon 01/03/2005 at 18:05       By: Leon Woestenberg <likewise>
Bug is reported to dissappear when the ARP queueing is limited to one packet 
per entry, so I limited the implementation to that. That fixes the bug, but 
leaves future work to see if a multi-packet queue can be implemented neatly.












For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=11400>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/







reply via email to

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