From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Tim Glaremin <Tim.Glaremin@web.de>
Subject: Re: [B.A.T.M.A.N.] Problem openWRT "backfire" and "kmod-batman-adv"
Date: Fri, 13 Aug 2010 05:24:22 +0200 [thread overview]
Message-ID: <201008130524.24059.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <4C6437BF.9080909@web.de>
[-- Attachment #1: Type: Text/Plain, Size: 1216 bytes --]
Tim Glaremin wrote:
> Hope it helps.... The part Marek quoted at least did change :)
The biggest problem is, that it is relative unreadable due to the reformatting
done by your mua. The next big problem is that the guessing will begin now
using the information in the stacktrace.
My first guess would be hardif_min_mtu. Maybe the netdev we want to access was
removed in the time we try to update our information of the
removed/deactivated interface (or another interface we also received some kind
of notification).
I would have guessed that this cannot happen because we haven't processed all
notification items, but I am awake a little bit too long to make 100% correct
statements.
Maybe because we use dev_put in hardif_deactivate_interface too early and
iterate over the already 'putted' device in our list (will be removed in
hardif_remove_interface from our list) - which seems to be wrong too me right
now. So all references will be gone when the interface goes down (so maybe it
will be completely deleted at that point), but the pointer to the destroyed
netdev is still in our list and will only deleted when the device will really
be unregistered.
thanks,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-08-13 3:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 18:04 [B.A.T.M.A.N.] Problem openWRT "backfire" and "kmod-batman-adv" Tim Glaremin
2010-08-13 3:24 ` Sven Eckelmann [this message]
2010-08-20 7:29 ` [B.A.T.M.A.N.] problem openwrt-trunk + ath5k + batman-adv-devel in my case Lemonde
2010-08-20 9:00 ` Sven Eckelmann
2010-08-20 16:24 ` Marek Lindner
2010-08-20 17:08 ` [B.A.T.M.A.N.] Where do we stand on working systems? Jon Roland
[not found] ` <AANLkTim6yVL8q=fXoFOu23ZBMpqaMHiheCV13-6U99+s@mail.gmail.com>
2010-08-20 20:10 ` Jon Roland
2010-08-21 5:01 ` [B.A.T.M.A.N.] problem openwrt-trunk + ath5k + batman-adv-devel in my case Kazuki Shimada
2010-08-21 6:01 ` Marek Lindner
2010-08-26 6:51 ` Kazuki Shimada
2010-08-26 8:28 ` Sven Eckelmann
2010-08-27 2:20 ` Kazuki Shimada
2010-08-27 9:59 ` Sven Eckelmann
2010-08-31 7:03 ` Kazuki Shimada
2010-08-31 9:32 ` Sven Eckelmann
[not found] ` <4C7E22B2.1000707@bb.banban.jp>
2010-09-01 10:48 ` Sven Eckelmann
2010-08-31 10:37 ` Marek Lindner
2010-09-01 10:04 ` Kazuki Shimada
2010-08-14 17:26 ` [B.A.T.M.A.N.] Problem openWRT "backfire" and "kmod-batman-adv" Marek Lindner
2010-08-16 16:51 ` Marek Lindner
[not found] <mailman.33.1282337388.934.b.a.t.m.a.n@lists.open-mesh.org>
2010-08-21 8:09 ` Tim
2010-08-21 8:15 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2010-08-18 6:42 Tim
[not found] ` <201008201211.51847.sven.eckelmann@gmx.de>
[not found] ` <4C6E8B79.7040801@web.de>
2010-08-20 14:44 ` Sven Eckelmann
2010-08-20 15:38 ` Sven Eckelmann
[not found] ` <4C6F5950.8070204@bb.banban.jp>
2010-08-21 6:19 ` Sven Eckelmann
2010-08-17 9:20 Tim
2010-08-17 9:27 ` Sven Eckelmann
2010-08-17 9:45 ` Tim
2010-08-17 9:51 ` Sven Eckelmann
2010-08-12 10:14 Tim Glaremin
2010-08-12 10:30 ` Marek Lindner
2010-08-12 10:32 ` Sven Eckelmann
[not found] <mailman.1.1281002401.15834.b.a.t.m.a.n@lists.open-mesh.org>
2010-08-11 10:47 ` Tim
2010-08-11 11:14 ` Marek Lindner
2010-08-11 11:20 ` Sven Eckelmann
2010-08-11 14:23 ` Tim
2010-08-11 14:52 ` Sven Eckelmann
2010-08-04 9:21 Tim
2010-08-04 9:34 ` Sven Eckelmann
2010-08-04 22:03 ` Marek Lindner
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=201008130524.24059.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=Tim.Glaremin@web.de \
--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