[Top][All Lists]

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

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

From: Jarno Malmari
Subject: [lwip-devel] [bug #57790] Fragmented UDP packets leads to crash on reassembly
Date: Wed, 12 Feb 2020 03:55:34 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.131 Safari/537.36

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

> > Is it ok for LWIP_RAM_HEAP_POINTER to be only for writing and RX only for
> 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:


  Message sent via Savannah

reply via email to

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