[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list
From: |
Sylvain Rochet |
Subject: |
[lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself |
Date: |
Tue, 21 Mar 2023 11:34:36 -0400 (EDT) |
Follow-up Comment #3, bug #63938 (project lwip):
Linked list corruption is the most common issue of contexts clash.
Please add support for LWIP_ASSERT_CORE_LOCKED (and LWIP_MARK_TCPIP_THREAD if
necessary) before anything else.
(As a side note, tcp_recved() is usually called from the TCP recv callback
and, as such, does not need locking).
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?63938>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Maximilian Mayr, 2023/03/17
- Message not available
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Maximilian Mayr, 2023/03/17
- Message not available
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Sylvain Rochet, 2023/03/17
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Maximilian Mayr, 2023/03/17
- Message not available
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself,
Sylvain Rochet <=
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Maximilian Mayr, 2023/03/27
- Message not available
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Maximilian Mayr, 2023/03/29
- Message not available
- [lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself, Sylvain Rochet, 2023/03/30