[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #21356] client thread freezes after MEMP_TCPIP_MSG sta
|
From: |
Marc Chaland |
|
Subject: |
[lwip-devel] [bug #21356] client thread freezes after MEMP_TCPIP_MSG starvation |
|
Date: |
Wed, 17 Oct 2007 11:00:21 +0000 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 |
Follow-up Comment #2, bug #21356 (project lwip):
OK, I didn't check out all the sources from CVS as I cannot get it through my
fw.
Into HEAD revision, TCPIP msg is taken from the stack. I don't understand how
another thread might asynchronously retrieve valid memory from this stack ?
Isn't this fix dangerous ?
I believe, memory should be allocated into tcpip_apimsg as into
sys_mbox_post. As a consequence sys_mbox_post may fail.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?21356>
_______________________________________________
Message posté via/par Savannah
http://savannah.nongnu.org/