[lwip-devel] [bug #27576] pbuf_realloc will assert or crash on a non-chained pbuf list

[Bill Auerbach]

Follow-up Comment #9, bug #27576 (project lwip):

If it's done in pbuf_free, the check will be less often and will also catch
pbuf corruption if this mismatch should occur after pbuf_realloc.

You're thinking:

LWIP_ASSERT("message",p->next!=NULL || p->len == p->tot_len);

I'm still not sure how things run so well for me with this error.  I've
modeled the same driver in 3 ports and all 3 wind up with len != tot_len on
packet receives.  Since I've only seen ping throw the error, maybe the check
in ping echo is sufficient?  lwIP seems to not be affected by the mismatch
otherwise.  If it can cause a problem, I don't think I've seen it (although
we've had one or 2 product crashes and possibly it is the pbuf_realloc while
loop that caused it).

    _______________________________________________________

Reply to this item at:

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

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