03e1872def
When application calls TCP connect(), the call is blocked by a semaphore which is then released when the connection is established. Unfortunately the semaphore release was done before the connection was marked as established. Depending on the configuration options set, it is possible that after the semaphore release, the thread that is waiting on connect() is run immediately. Because of this, the connection bookeeping still thought that the connection was not established even if it was. A simple solution is to release the semaphore after the connection is marked as established. Fixes #35390 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com> |
||
|---|---|---|
| .. | ||
| ip | ||
| l2 | ||
| lib | ||
| buf.c | ||
| CMakeLists.txt | ||
| hostname.c | ||
| Kconfig | ||
| Kconfig.hostname | ||
| Kconfig.template.log_config.default.net | ||
| Kconfig.template.log_config.net | ||