tree 44d42610560d93968338fcdd8268c2bd0fc9119d
parent 5f68ea686dece64172ab0b106df090e8028cf316
author Robert Lubos <robert.lubos@nordicsemi.no> 1684925632 +0200
committer Anas Nashif <anas.nashif@intel.com> 1685109313 -0400

net: sockets: tcp: Fix possible race between connect/recv

Installing recv callback with net_context_recv() after
net_context_connect() left an opening for a possible race - in case the
server send some data immediately after establishing TCP connection, and
Zephyr did not manage to install the callback on time, the data would be
lost, corrupting the stream.

This can be avoided, by installing the recv callback before the
connection is triggered. As net_context_recv() called w/o timeout only
registers the callback function, it should have no negative impact. The
only change on the TCP side is when the connection is closed - in case
TCP is in connect stage, do not call the recv callback (before this
change it'd be NULL at that point).

Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>