[lwip-devel] [bug #57790] Fragmented UDP packets leads to crash on reassembly

[Jarno Malmari]

Follow-up Comment #4, bug #57790 (project lwip):

> Are you at least sure it's not a threading issue?
Yes. My app is single threaded. The public example happened to be multi.

> 
> If you could send a simple udp API level application to test against, I
could try to test that on another target...
> 
No udp api code is even needed. Simple loop running just the lwip stack is
enough.

> > Is it ok for LWIP_RAM_HEAP_POINTER to be only for writing and RX only for
reading?
> 
> I'm afraid I don't understand that.
Sorry, I wasn't clear. I mean the lwip is given a pool that may be write only
(that eth dma will read). For lwip input, a custom pbuf is allocated from
external pool that may be read only (that eth dma wrote). I just wonder
whether it's safe to assume lwip doesn't use pbuf payloads in a conflicting
way under the hood.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?57790>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/