[lwip-devel] [bug #66230] LWIP assert "pbuf_free: p->ref > 0" and "tcpip_thread: Invalid message" reported in lwip 2.2.0

[David Cermak]

Follow-up Comment #4, bug #66230 (group lwip):


> Re comment #1:

Thanks for explaining that the scenario with two threads reading  is not
supported. (Sorry for hijacking this thread, should have created a new
issue).

> we support 1 thread reading and 1 thread writing

Yes, can see it now that this is documented:

/** LWIP_NETCONN_FULLDUPLEX==1: Enable code that allows reading from one
thread,
* writing from a 2nd thread and closing from a 3rd thread at the same time.
* LWIP_NETCONN_SEM_PER_THREAD==1 is required to use one socket/netconn from
* multiple threads at once!
 */
(was a bit confused by the `LWIP_NETCONN_SEM_PER_THREAD` option).


PS: We'll probably go ahead and fix this in the esp-lwip port using the extra
lock method (option 1). I understand it's not a common scenario, but we use it
in our case to serve an HTTP server with multiple worker threads (will also
likely make it configurable).

Thanks again for the clarification!


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature