From: Hangbin Liu <liuhangbin@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Felix Fietkau <nbd@nbd.name>, John Crispin <john@phrozen.org>,
Jo-Philipp Wich <jo@mein.io>
Subject: Re: Regression: net/ipv6/mld running system out of memory (not a leak)
Date: Wed, 12 Feb 2020 16:24:34 +0800 [thread overview]
Message-ID: <20200212082434.GM2159@dhcp-12-139.nay.redhat.com> (raw)
In-Reply-To: <CACna6rwD_tnYagOPs2i=1jOJhnzS5ueiQSpMf23TdTycFtwOYQ@mail.gmail.com>
On Wed, Feb 12, 2020 at 08:37:31AM +0100, Rafał Miłecki wrote:
> Hi, I need some help with my devices running out of memory. I've
> debugging skills but I don't know net subsystem.
>
> I run Linux based OpenWrt distribution on home wireless devices (ARM
> routers and access points with brcmfmac wireless driver). I noticed
> that using wireless monitor mode interface results in my devices (128
> MiB RAM) running out of memory in about 2 days. This is NOT a memory
> leak as putting wireless down brings back all the memory.
>
> 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 regression was introduced by the commit 1666d49e1d41 ("mld: do
> not remove mld souce list info when set link down") - first appeared
> in 4.10 and then backported. This bug exists in 4.9.14 and 4.14.169.
> Reverting that commit from 4.9.14 and 4.14.169 /fixes/ the problem.
>
> Can you look at possible cause/fix of this problem, please? Is there
> anything I can test or is there more info I can provide?
Hi Rafał,
Thanks for the report. Although you said this is not a memory leak. Maybe
you can try a84d01647989 ("mld: fix memory leak in mld_del_delrec()").
Thanks
Hangbin
>
> I'm not sure why this issue appears only when using monitor mode.
> Using wireless __ap mode interface (with hostapd) won't expose this
> issue. I guess it may be a matter of monitor interfaces not being
> bridged?
>
> --
> Rafał
next prev parent reply other threads:[~2020-02-12 8:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 7:37 Regression: net/ipv6/mld running system out of memory (not a leak) Rafał Miłecki
2020-02-12 7:59 ` Eric Dumazet
2020-02-12 8:46 ` Rafał Miłecki
2020-02-12 8:24 ` Hangbin Liu [this message]
2020-02-12 8:49 ` Rafał Miłecki
2020-02-12 10:08 ` Hangbin Liu
2020-02-18 6:55 ` Rafał Miłecki
2020-02-18 8:27 ` Hangbin Liu
2020-02-18 8:08 ` Rafał Miłecki
2020-02-18 8:53 ` Hangbin Liu
2020-03-03 6:16 ` Rafał Miłecki
2020-03-03 9:00 ` Hangbin Liu
2020-03-03 9:11 ` Hangbin Liu
2020-03-03 9:23 ` Rafał Miłecki
2020-03-03 9:26 ` Hangbin Liu
2020-03-04 6:45 ` Hangbin Liu
2020-03-04 7:44 ` Rafał Miłecki
2020-03-04 9:07 ` Hangbin Liu
2020-03-04 10:07 ` Rafał Miłecki
2020-03-05 4:02 ` Hangbin Liu
2020-03-06 11:14 ` Rafał Miłecki
2020-03-09 8:33 ` Hangbin Liu
2020-03-09 12:31 ` Rafał Miłecki
2020-03-10 7:09 ` Hangbin Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200212082434.GM2159@dhcp-12-139.nay.redhat.com \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=jo@mein.io \
--cc=john@phrozen.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).