|
From: | address@hidden |
Subject: | Re: [lwip-commits] [SCM] lwIP Contrib - Contributed code for Lightweight TCP/IP stack branch, master, updated. STABLE-2_0_0_RELEASE-191-g4c854d4 |
Date: | Tue, 2 Jan 2018 19:40:06 +0100 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Joel Cunningham wrote:
[..] which showed the problems in bug #52719 and also some other problems with tcpip_init() and executing the initfunc (which currently does not have the core lock held).
We were already talking about the init phase earlier this day. The problem here is that with our systems, the init phase is executed before the OS is started (and all threads are of course created suspended until the scheduler is started). In this setup, you can't acquire the core lock (e.g. calling netif_add() after tcpip_init() from your main function).
If you're talking about the fact the the init callback is called from tcpip_thread without the lock held, go ahead and fix it - you're right ;-)
Cheers, Simon
[Prev in Thread] | Current Thread | [Next in Thread] |