From: Russell Senior <russell@personaltelco.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batman-adv: memory leak?
Date: Wed, 22 Jan 2014 11:18:09 -0800 [thread overview]
Message-ID: <86txcvomfi.fsf@coulee.tdb.com> (raw)
In-Reply-To: <52E003DD.6040302@meshcoding.com> (Antonio Quartulli's message of "Wed\, 22 Jan 2014 18\:46\:05 +0100")
>>>>> "Antonio" == Antonio Quartulli <antonio@meshcoding.com> writes:
Russell> Has anybody else seen this memory leak? Leads on where it's
Russell> coming from? Not a runaway process, at least not that top
Russell> shows up. Just a gradual disappearance from MemFree that
Russell> /proc/sys/vm/drop_caches doesn't fix. It isn't adhoc mode,
Russell> and I can associate the two devices over adhoc and move a
Russell> bunch of data with no memory lost, but turning on batman-adv
Russell> seems to sink it.
Russell> The memory leak I see seems to commence as soon as a
Russell> batman-adv neighbor (same version, in this case 15) appears
Russell> and stops when the neighbor goes away.
Antonio> Thank you very much for the hint Russel! Today I tried with
Antonio> one node only, but kmemleak did not report anything...
Russell> I am going to try enabling kmemleak and see of that tells me
Russell> anything.
Antonio> Thanks! Keep us informed!
Here is a bootlog in which I spit out a bunch of kmemleak stuff into a
console (captured by /usr/bin/screen, sorry for the extraneous line
feed silliness).
https://personaltelco.net/~russell/kmemleak-batman-from-boot.log
If I count instances, it looks like batadv_orig_node_vlan_new (and the
things that are calling it) may be implicated.
Hope that helps!
--
Russell Senior, President
russell@personaltelco.net
next prev parent reply other threads:[~2014-01-22 19:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 10:22 [B.A.T.M.A.N.] [PATCH maint] batman-adv: fix soft-interface MTU computation Antonio Quartulli
2014-01-21 10:31 ` Antonio Quartulli
2014-01-27 7:57 ` Marek Lindner
2014-01-21 18:43 ` Russell Senior
2014-01-21 19:00 ` Antonio Quartulli
2014-01-22 6:04 ` Russell Senior
2014-01-22 7:03 ` Antonio Quartulli
2014-01-22 7:04 ` [B.A.T.M.A.N.] memleak (Was: [PATCH maint] batman-adv: fix soft-interface MTU computation) Antonio Quartulli
2014-01-22 7:37 ` [B.A.T.M.A.N.] [PATCH maint] batman-adv: fix soft-interface MTU computation Daniel
2014-01-22 17:45 ` [B.A.T.M.A.N.] batman-adv: memory leak? Russell Senior
2014-01-22 17:46 ` Antonio Quartulli
2014-01-22 19:18 ` Russell Senior [this message]
2014-01-22 20:49 ` cmsv
2014-01-22 23:57 ` Russell Senior
2014-01-23 0:10 ` cmsv
2014-01-23 3:35 ` Daniel
2014-01-26 12:57 ` Daniel
2014-01-26 14:21 ` Antonio Quartulli
2014-01-26 14:24 ` [B.A.T.M.A.N.] [PATCH maint] batman-adv: release vlan object after checking the CRC Antonio Quartulli
2014-01-27 18:43 ` Russell Senior
2014-01-26 16:05 ` [B.A.T.M.A.N.] batman-adv: memory leak? cmsv
2014-01-26 16:07 ` Antonio Quartulli
2014-01-26 16:13 ` Antonio Quartulli
2014-01-27 17:55 ` cmsv
2014-01-28 1:21 ` Russell Senior
2014-01-28 1:30 ` cmsv
2014-01-29 8:10 ` Russell Senior
2014-01-29 21:48 ` cmsv
2014-02-08 3:08 ` cmsv
2014-02-08 10:53 ` Felix Fietkau
2014-02-12 7:23 ` Antonio Quartulli
2014-02-12 10:40 ` cmsv
2014-02-12 11:41 ` Antonio Quartulli
2014-02-13 0:55 ` cmsv
2014-02-13 7:23 ` Antonio Quartulli
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=86txcvomfi.fsf@coulee.tdb.com \
--to=russell@personaltelco.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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