b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batman-adv: memory leak?
Date: Sun, 26 Jan 2014 15:21:56 +0100	[thread overview]
Message-ID: <52E51A04.8020800@meshcoding.com> (raw)
In-Reply-To: <52E5063E.3080408@makrotopia.org>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

On 26/01/14 13:57, Daniel wrote:
> I now built OpenWrt trunk/BB r39365 with batman-adv 2013.4.0 instead of
> 2014.0.0, tried with all possible settings, no memory leak what-so-over, happy
> uptimes of more than a day by now :)
> all other system components and settings are exactly identical to my previous
> setup with batman-adv 2014.0.0.
> 
> On 01/23/2014 04:35 AM, Daniel wrote:
>> On 01/23/2014 01:10 AM, cmsv wrote:
>>> what version are you using ?
> 
>> out-of-memory every 20 minutes or so on OpenWrt trunk/BB r39365 on tl-wr841nd-v8
>> with batman-adv 2014.0.0 from openwrt's routing feed with "batman-adv: fix
>> batman-adv header overhead calculation" and "batman-adv: fix soft-interface MTU
>> computation" on top.
>> A sample node is (occasionally) reachable via DN42 at 104.61.99.104 (feel free
>> to ask for ssh or any kind of logs, serial access, remote gdb or whatever)
> 

Thanks for testing guys!

I found something wrong in the code and I am going to send a patch soon.
I'd really appreciate if somebody could test it!

Thanks!

-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-01-26 14:21 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
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 [this message]
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=52E51A04.8020800@meshcoding.com \
    --to=antonio@meshcoding.com \
    --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;
as well as URLs for NNTP newsgroup(s).