[riot-notifications] [RIOT-OS/RIOT] gcoap server breaks or becomes very unresponsive (sock_async related?) (#14034)

Martine Lenders notifications at github.com
Tue May 12 13:47:31 CEST 2020

Hi, other than the CoAP messages themselves, the sock should not signal any other UDP messages. It might indeed however be, that there is more than one CoAP message hidden behind the `RECV` signal. @MichelRottleuthner is right in his observation, that this _should_ trigger another `RECV` after the previous is handled. This is however not the case, and should rather be fixed, than with the workaround you proposed. Could you check if

diff --git a/sys/net/gnrc/sock/gnrc_sock.c b/sys/net/gnrc/sock/gnrc_sock.c
index a1c22d77f..c6d0c2181 100644
--- a/sys/net/gnrc/sock/gnrc_sock.c
+++ b/sys/net/gnrc/sock/gnrc_sock.c
@@ -150,6 +150,11 @@ ssize_t gnrc_sock_recv(gnrc_sock_reg_t *reg, gnrc_pktsnip_t **pkt_out,
     *pkt_out = pkt; /* set out parameter */
+    if (reg->async_cb.generic && cib_avail(&reg->mbox.cib)) {
+        reg->async_cb.generic(reg, SOCK_ASYNC_MSG_RECV, reg->async_cb_arg);
+    }
     prevpkt = pkt;

fixes this?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200512/71153ff2/attachment.htm>

More information about the notifications mailing list