On 2018-07-11 11:52 AM, Voina Alex wrote:
Dear OpenWRT/LEDE buddy,
I have found a bug in the Chaos Calmer (15.05.1 , 448532) release that
has been fixed since the lede-17.01.3 release for x86 targets. The bug
is related to ubusd or libubox but I'm not really sure which one it is.
It is a file descriptor leak rooted in the logread ubus method. Every
call to logread whether is logread -f, logread, logread -l 1 or ubus
call log read '{ }' opens a file of the following format which is not
closed anymore.
ubusd 2918 root 41r CHR 1,3 0t0 3934 /dev/null
ubusd 2918 root 42r CHR 1,3 0t0 3934 /dev/null
ubusd 2918 root 43r CHR 1,3 0t0 3934 /dev/null
ubusd 2918 root 44r CHR 1,3 0t0 3934 /dev/null
ubusd 2918 root 45r CHR 1,3 0t0 3934 /dev/null
ubusd 2918 root 46r CHR 1,3 0t0 3934 /dev/null
ubusd 2918 root 47r CHR 1,3 0t0 3934 /dev/null
I saw this issue is mitigated in lede-17.01.3 but I don't know where
exactly along the releases it happened. Can you point me to the
patch/commit that fixes this ?
This is perhaps a silly question but did you look at the ubus repo at
git.openwrt.org (ubus source code is maintained separate from the main
tree; the main tree is primarily packaging/build and kernel concerns.
Regards,
Daniel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
