[OpenWrt-Devel] Wireless monitor interface causes device to run out of memory

Felix Fietkau nbd at nbd.name
Tue Feb 11 11:21:14 EST 2020

On 2020-02-11 17:03, Rafał Miłecki wrote:
> On Wed, 5 Feb 2020 at 11:14, Rafał Miłecki <zajec5 at gmail.com> wrote:
>> I noticed that my bcm53xx devices run out of memory after running
>> wireless monitor interface for about 2 days.
>> This problem occurs since 0694d08c84fd ("bcm53xx: switch to kernel
>> 4.9") which bumped kernel from 4.4.53 to 4.9.14 and is still present
>> when using 4.14.
>> Interestingly this memory drain requires at least one of:
>> net.ipv6.conf.default.forwarding=1
>> net.ipv6.conf.all.forwarding=1
>> to be set. OpenWrt happens to use both by default.
>> This is *not* a memory leak. Restarting wireless interfaces frees all
>> consumed memory.
>> Any idea what may be causing this?
> This regression is caused by 1666d49e1d41 ("mld: do not remove mld
> souce list info when set link down") which was later backported as
> 53a76d633b86 to the linux-4.9.y branch.
> Reverting that commit from 4.9.14 or 4.14.169 /fixes/ device running
> out of memory problem.
Looks like it's missing a backport of

commit a84d016479896b5526a2cc54784e6ffc41c9d6f6
"[PATCH net] mld: fix memory leak in mld_del_delrec()"

- Felix

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

More information about the openwrt-devel mailing list