lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] [bug #11400] ARP multi-packet-queue modifies TCP unsent/una


From: Jonathan Larmour
Subject: [lwip-devel] [bug #11400] ARP multi-packet-queue modifies TCP unsent/unacked segment packet pbuf chain into packet queue
Date: Thu, 05 Apr 2007 10:39:52 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070223 Fedora/1.5.0.10-1.fc5 Firefox/1.5.0.10

Follow-up Comment #42, bug #11400 (project lwip):

Re copying PBUF_RAMs: that's what I was discussing in comment #35 (and was
what I thought you had raised in comment #34). As far as I know, users are
allowed to reuse data including pbufs without needing to check their ref
count. That's why there's a "copy" flag to netconn_write/tcp_write, for
example. I assume UDP or other protocols (ICMP, and whatever other packets
artificially constructed by the user etc.) are analogous. Although at the
same time, we don't need to copy a PBUF_RAM if it's part of a TCP seg - we
know that is controlled by lwIP. Is there any way we can detect and avoid a
pbuf_copy for this?

For UDP and other protocols, we theoretically could change the API contract
here and say that users can't reuse pbufs (or their payload) until their ref
count returns to 1 (from a higher value set within the stack). I don't think
that's right personally, but it's Kieran's call really.


    _______________________________________________________

Reply to this item at:

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

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





reply via email to

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