uloop: do not use ULOOP_EDGE_TRIGGER for the blocking socket, it can miss some events due to races
This commit is contained in:
parent
a204ae358b
commit
c0c06ec7ea
1 changed files with 1 additions and 1 deletions
|
@ -150,7 +150,7 @@ const char *ubus_strerror(int error);
|
||||||
|
|
||||||
static inline void ubus_add_uloop(struct ubus_context *ctx)
|
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 */
|
/* call this for read events on ctx->sock.fd when not using uloop */
|
||||||
|
|
Loading…
Reference in a new issue