|
From: | Joel Cunningham |
Subject: | [lwip-devel] [task #14420] Remove sys_sem_signal from inside SYS_ARCH_PROTECT crit section |
Date: | Wed, 19 Jul 2017 10:42:44 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 |
Update of task #14420 (project lwip): Percent Complete: 100% => 90% Open/Closed: Closed => Open _______________________________________________________ Follow-up Comment #8: I was auditing the changes for this task again and I believe there is an outstanding synchronization issue for the TCPIP_CORE_LOCKING case. The premise of the change was that the core lock would be held when event_callback is executed and then select code in sockets.c could use the core lock to also protect select_cb_list The problem is there are some places where event_callback (called via API_EVENT) is not within core locking code. These are for cases where sockets/netconn is taking things from their mboxes. Here's the list I'm seeing: netconn_accept netconn_recv_data netconn_recv_data_tcp _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/task/?14420> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |