[OpenWrt-Devel] [PATCH][RFC] libubus: added max retry mechanism

Felix Fietkau nbd at openwrt.org
Tue Jul 29 09:30:36 EDT 2014

On 2014-07-29 15:23, Alexandru Ardelean wrote:
> Quick info follow-up:  strace-ing on the PIDs (with high CPU usage)
> shows a lot of EAGAIN errors from recvfrom() and a lot of recvfrom() +
> poll() + clock_gettime_monotonic() calls.
> Thinking about it, would it make more sense to add a short wait instead
> [to reduce the throttle] and let it "infinitely" loop ?  ["infinitely"
> loop == loop until it does not error with EAGAIN]
I think it's much more likely that this is a bug, caused by errors on
the ubus socket not being caught or handled properly.
If that is the case, then both approaches are wrong, and we should just
handle the error correctly.
Can you figure out what triggers this behavior?

- Felix
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list