Re: Finding memory leak

[Holger Kiehl]

On Sat, 18 Oct 2003, Jörn Engel wrote:

> On Sat, 18 October 2003 19:46:36 +0200, Jörn Engel wrote:
> > On Sat, 18 October 2003 19:23:53 +0200, Jörn Engel wrote:
> > > > 
> > > >   - Could someone please check igmpv3_newpack() and assure me that there
> > > >     is no leak.
> > > 
> > > There was a leak, found by the stanford checker team.  I've provided a
> > > broken fix, DaveM wanted to write a decent one.  Not sure if it has
> > > already found it's way into the official kernel.
> > 
> > If DaveM hasn't fixed it yet, you can also try this patch.  Since I'm
> > pretty unaware of the networking code, this may be broken again, but
> > it also can't make things much worse for you.
> 
> Or this one.  igmpv3_newpack() is to a large degree identical to
> igmp_send_report().  The latter doesn't have a memleak, so I basically
> adjusted the former to behave identical.  Should be foolproof, even
> for me.
> 
Did try this, but the leak is still there. The size-2048 values is always
slowly going up.

Holger

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/