From: Felix Fietkau Date: Fri, 18 May 2012 20:32:25 +0000 (+0200) Subject: uloop: do not use ULOOP_EDGE_TRIGGER for the blocking socket, it can miss some events... X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=c0c06ec7ead11ca201bcbf0d1c7e986c7d3c90c0;p=oweals%2Fubus.git uloop: do not use ULOOP_EDGE_TRIGGER for the blocking socket, it can miss some events due to races --- diff --git a/libubus.h b/libubus.h index 0dcbb6d..e0e418b 100644 --- a/libubus.h +++ b/libubus.h @@ -150,7 +150,7 @@ const char *ubus_strerror(int error); static inline void ubus_add_uloop(struct ubus_context *ctx) { - uloop_fd_add(&ctx->sock, ULOOP_EDGE_TRIGGER | ULOOP_BLOCKING | ULOOP_READ); + uloop_fd_add(&ctx->sock, ULOOP_BLOCKING | ULOOP_READ); } /* call this for read events on ctx->sock.fd when not using uloop */