From: "Martin Hundebøll" <martin@hundeboll.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.] kernel BUG at net/core/skbuff.c:100
Date: Thu, 20 Nov 2014 11:27:32 +0100 [thread overview]
Message-ID: <546DC214.6050908@hundeboll.net> (raw)
In-Reply-To: <1416476912.2747.5.camel@gmail.com>
Hi Philipp,
On 2014-11-20 10:48, Philipp Psurek wrote:
> Hi Martin,
>
> Thank you for your response. I'm glad to help making Batman-adv better.
>
> Batman-adv ran with network_coding enabled while kernel panic. This was
> a misconfiguration because our nodes doesn't have nc compiled in their
> Batman kernel module. The VM is in production. I deactivated nc after
> someone told me I do not need nc. But I think my community forgive me
> another gateway failure for research sake.
Yeah, most people compile out network coding. Has the bug disappeared
after disabling NC ?
> Am Donnerstag, den 20.11.2014, 09:32 +0100 schrieb Martin Hundebøll:
>> Thanks for you report. The bug is probably triggered by some bogus data
>> in an incoming packet. I have created a small debug patch that will
>> detect if this is the case, and print some debug info if so.
>
> Thank you for your work. I didn't find your Patch on
> http://git.open-mesh.org/batman-adv.git
It was attached to my previous mail :)
> I can not analyse the packages because the gateway is part of an ISP
> infrastructure and there is data privacy. But if you're capable to fish
> only the bogus data package during kernel panic with your patch there
> shouldn't be any problems, I think.
My debug patch should only print the header of the packet causing the
panic, so no problems with privacy here. (But you should probably check
the output before mailing it to a public list...)
>> Is it possible for you to checkout the source, add the patch, and
>> compile the module?
>
> Yes, I can checkout, patch and compile. The kernel is compiled with
> CONFIG_DEBUG_INFO=y
> # CONFIG_DEBUG_INFO_REDUCED is not set
> # CONFIG_ENABLE_WARN_DEPRECATED is not set
>
> Batman-adv is compiled as module. Is there a reboot of the VM needed if
> I patch the source, compile, replace, depmod and reload the Batman
> module?
A simple rmmod/insmod should be enough. (Including the following
configuration, which is reset with rmmod.)
> Please send me the patch and tell me the additional make parameters to
> compile the module with debug symbols. Is it something like
> make \
> CONFIG_BATMAN_ADV_DEBUG=y \
> CONFIG_BATMAN_ADV_BLA=y \
> CONFIG_BATMAN_ADV_DAT=y \
> CONFIG_BATMAN_ADV_NC=y
> ?
> If I patch the (batman) kernel sources directly then a simply make in
> kernel directory should be enough, I presume. I also presume vmimage
> will be updated. Or should I rebuild the kernel from scratch?
Running make (as you write it above) in the module directory should do
the trick. (Given you have the needed kernel header files installed)
E.g. something like this:
git clone --branch v2014.3.0 git://git.open-mesh.org/batman-adv.git
cd batman-adv
git apply frag_debug_size.patch
make \
CONFIG_BATMAN_ADV_DEBUG=y \
CONFIG_BATMAN_ADV_BLA=y \
CONFIG_BATMAN_ADV_DAT=y \
CONFIG_BATMAN_ADV_NC=y
sudo rmmod batman_adv
sudo insmod batman-adv.ko
sudo batctl if add fastd0
And then your usual IP configuration on bat0 etc.
> I hope, this bug doesn't occur through the gentoo patches. But some
> similar freezes happened on Arch Linux with 3.14.23_ARCH and 3.17.1-ARCH
> with nc enabled. Unfortunately I can not analyse this bug on the Arch
> VMs because I'm not in total control of their VM terminal.
I am running with NC on my machines in the lab and haven't seen this
frag-issue before. I have seen a similar issue (wrong size value in the
header) in another context though, but this wasn't due to either network
coding or fragmentation.
Would you mind sending me your fastd config (without the key), so that I
can try to reproduce this in my VMs?
Thanks,
Martin
next prev parent reply other threads:[~2014-11-20 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 21:58 [B.A.T.M.A.N.] kernel BUG at net/core/skbuff.c:100 Philipp Psurek
2014-11-20 8:32 ` Martin Hundebøll
2014-11-20 9:48 ` Philipp Psurek
2014-11-20 10:27 ` Martin Hundebøll [this message]
2014-11-20 12:22 ` Philipp Psurek
2014-11-20 12:36 ` Martin Hundebøll
2014-11-21 8:40 ` Philipp Psurek
2014-11-22 20:39 ` Philipp Psurek
2014-11-24 8:24 ` Martin Hundebøll
2014-11-24 10:44 ` Philipp Psurek
2014-11-24 12:14 ` Philipp Psurek
2014-11-24 21:15 ` Philipp Psurek
2014-11-24 22:26 ` Philipp Psurek
2014-11-25 0:22 ` Philipp Psurek
2014-11-25 10:17 ` Philipp Psurek
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=546DC214.6050908@hundeboll.net \
--to=martin@hundeboll.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