public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv-kernelland: Fix memory corruption bug
Date: Fri, 5 Dec 2008 20:51:31 +0100	[thread overview]
Message-ID: <20081205195131.GA27271@pandem0nium> (raw)
In-Reply-To: <C12B8956-7F83-4FBE-A300-B803928CB64C@gmail.com>

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

Hey Scott,

On Fri, Dec 05, 2008 at 11:40:30PM +1300, Scott Raynel wrote:
> Hi Simon,
> 
> On 5/12/2008, at 12:35 AM, Simon Wunderlich wrote:
> 
> >Hey Scott,
> >
> >thank you very much for the fix! Can you confirm if this bug is  
> >related
> >to https://dev.open-mesh.net/batman/ticket/86 ?
> >This bug has very likely been caused by a memory corruption, but i
> >couldn´t find where. (i have not experienced any kernel panics by  
> >this
> >however ...).
> 
> 
> It is quite possible that they are related. The slab error states that  
> a memory allocation was overwritten - the same problem as my patch  
> fixed. However, I can't confirm whether it is the same memory  
> allocation or a different one. The stack trace I got specifically  
> mentioned the kfree() in send_own_packet(), whereas this stack trace  
> does not.
> 
> Is that bug easily reproducible? It will be a couple of days before I  
> can try to look at it.

Yep, it was quite easy: just turn it on and off a few times. (echo
device and nothing into /proc/net/batman-adv/interfaces). The warning
appeared after 10 times in my qemu instance. No crash, only this warning.
> 
> Also, the stack trace is confusing as it appears to indicate a kfree()  
> within hardif_min_mtu(), which I can't find :)

That's the problem, that is what confused me at this point. :/

> 
> I'll try to do some stress testing of the module with the slab  
> debugger turned on for a while and see what happens.

Sounds great. Thanks for you hard work. :)

best regards,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-12-05 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  1:14 [B.A.T.M.A.N.] [PATCH] batman-adv-kernelland: Fix memory corruption bug Scott Raynel
2008-12-04  2:30 ` Marek Lindner
2008-12-04 11:35 ` Simon Wunderlich
2008-12-05 10:40   ` Scott Raynel
2008-12-05 19:51     ` Simon Wunderlich [this message]
2008-12-12  9:08       ` Scott Raynel

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=20081205195131.GA27271@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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