SPRESENSE opened a new issue, #10977: URL: https://github.com/apache/nuttx/issues/10977
It seems that there is a bug that causes connect() to fail with an EACCES error when CONFIG_NET_USRSOCK is enabled. This bug appears to have been introduced in the PR of https://github.com/apache/nuttx/pull/7291 When a UDP socket is created and connect() is executed, between usrsock_setup_request_callback() and do_connect_request(), the USRSOCK_EVENT_SENDTO_READY event is sent by the usock daemon for that created socket, it seems that do_connect_request() will return EACCES. Since a UDP socket can be sent anytime upon creation, it is a regular case that a USRSOCK_EVENT_SENDTO_READY event is sent at this time. Therefore, I think the problem is that conncet() causes an error when the USRSOCK_EVENT_SENDTO_READY event is sent during the above gap. Could you please consider a countermeasure? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
