WPS UPnP: Handle HTTP initiation failures for events more properly

While it is appropriate to try to retransmit the event to another
callback URL on a failure to initiate the HTTP client connection, there
is no point in trying the exact same operation multiple times in a row.
Replve the event_retry() calls with event_addr_failure() for these cases
to avoid busy loops trying to repeat the same failing operation.

These potential busy loops would go through eloop callbacks, so the
process is not completely stuck on handling them, but unnecessary CPU
would be used to process the continues retries that will keep failing
for the same reason.

Signed-off-by: Jouni Malinen <jouni@codeaurora.org>

diff --git a/src/wps/wps_upnp_event.c b/src/wps/wps_upnp_event.c
index 08a23612f3382337438d67c7a5c54f43979951ac..c0d9e41d9a38eb60067d0f94236ca4e5ea5f1c19 100644 (file)
--- a/src/wps/wps_upnp_event.c
+++ b/src/wps/wps_upnp_event.c
@@ -294,7 +294,7 @@ static int event_send_start(struct subscription *s)
 
        buf = event_build_message(e);
        if (buf == NULL) {
-               event_retry(e, 0);
+               event_addr_failure(e);
                return -1;
        }
 
@@ -302,7 +302,7 @@ static int event_send_start(struct subscription *s)
                                         event_http_cb, e);
        if (e->http_event == NULL) {
                wpabuf_free(buf);
-               event_retry(e, 0);
+               event_addr_failure(e);
                return -1;
        }